unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#65811: 27.1; zzzzzzzz forever
@ 2023-09-07 20:33 Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  5:47 ` Eli Zaretskii
  0 siblings, 2 replies; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-07 20:33 UTC (permalink / raw)
  To: 65811

[-- Attachment #1: Type: text/plain, Size: 8435 bytes --]

I have observed two issues while running emacs under WSL2 (Ubuntu 22.04)
on Windows 11.
I know this is a heresy but it should still work and does mostly.

This bug report concerns issue one which is that sometimes
my emacs inexplicably starts filling with repeated zzzzzzz characters.
Though other editing activity is possible inbetween 'attacks'

This continues even if I unplug the keyboard (to rule out a USB keyboard
issue).zzzzzzzzzzzzzzzzzzzzzzz
It is possible to get control back temporarily by changing the window
size.zzzzzzzzzzzzzz
The added zzzzz... can be undone using ctrl-u.

This only happens to me with emacs under WSL.
Not with emacs running under cygin
or in a genuine linux host.
Though I have a suspicion it might relates to pressing ctrl-z somehow.

I have also observed a possibly related hang.

My second issue is that if left running (typically unattended or out of
focus) for a long time emacs crashes. I will try to add a second bug report
with a backtrace when this happens.
I did not have the debug symbols installed for previous occurances but
it is quite repeatable.

I had hoped the most recent update would fix this but it doesn't.

    emacs (1:27.1+1-3ubuntu5.1) jammy; urgency=medium

      * debian/patches/0001-Use-a-64KB-page-size-for-pdump.patch: cherry-pick
        a change from upstream that fixes a crash when booted on a 64K page
        kernel on arm64. LP: #2030892.

I have a couple of backtraces below for the zzzz issue:

Reading symbols from emacs...
Reading symbols from /usr/lib/debug/.build-id/96/8bd488365ca5ef23edbd3ff2265fa59c1ed52e.debug...
Attaching to program: /usr/bin/emacs, process 31835
[New LWP 31836]
[New LWP 31837]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pselect64_syscall (sigmask=<optimized out>, timeout=<optimized out>, exceptfds=0x0, writefds=0x7ffdcff6aad0, readfds=0x7ffdcff6aa50, nfds=7) at ../sysdeps/unix/sysv/linux/pselect.c:34
34      ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
(gdb) where
#0  pselect64_syscall (sigmask=<optimized out>, timeout=<optimized out>, exceptfds=0x0, writefds=0x7ffdcff6aad0, readfds=0x7ffdcff6aa50, nfds=7) at ../sysdeps/unix/sysv/linux/pselect.c:34
#1  __pselect (nfds=7, readfds=0x7ffdcff6aa50, writefds=0x7ffdcff6aad0, exceptfds=0x0, timeout=<optimized out>, sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/pselect.c:56
#2  0x000056552f834785 in really_call_select (arg=0x7ffdcff6a960) at ./debian/build-src/src/thread.c:586
#3  0x000056552f83551d in thread_select (func=<optimized out>, max_fds=max_fds@entry=7, rfds=rfds@entry=0x7ffdcff6aa50, wfds=wfds@entry=0x7ffdcff6aad0, efds=efds@entry=0x0,
    timeout=timeout@entry=0x7ffdcff6b070, sigmask=0x0) at ./debian/build-src/src/thread.c:616
#4  0x000056552f85238f in xg_select (fds_lim=7, rfds=rfds@entry=0x7ffdcff6b180, wfds=wfds@entry=0x7ffdcff6b200, efds=efds@entry=0x0, timeout=timeout@entry=0x7ffdcff6b070,
    sigmask=sigmask@entry=0x0) at ./debian/build-src/src/xgselect.c:117
#5  0x000056552f812319 in wait_reading_process_output (time_limit=time_limit@entry=30, nsecs=nsecs@entry=0, read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
    wait_for_cell=wait_for_cell@entry=0x0, wait_proc=wait_proc@entry=0x0, just_wait_proc=0) at ./debian/build-src/src/process.c:5571
#6  0x000056552f676d53 in sit_for (timeout=timeout@entry=0x7a, reading=reading@entry=true, display_option=display_option@entry=1) at ./debian/build-src/src/dispnew.c:6056
#7  0x000056552f75d494 in read_char (commandflag=1, map=0x5655312ca9d3, prev_event=0x0, used_mouse_menu=0x7ffdcff6ba4b, end_time=0x0) at ./debian/build-src/src/keyboard.c:2738
#8  0x000056552f75db6a in read_key_sequence (keybuf=<optimized out>, prompt=0x0, dont_downcase_last=<optimized out>, can_return_switch_frame=true, fix_current_buffer=true,
    prevent_redisplay=<optimized out>) at ./debian/build-src/src/keyboard.c:9553
#9  0x000056552f75f30c in command_loop_1 () at ./debian/build-src/src/keyboard.c:1350
#10 0x000056552f7ccf67 in internal_condition_case (bfun=bfun@entry=0x56552f75f110 <command_loop_1>, handlers=handlers@entry=0x90, hfun=hfun@entry=0x56552f755a80 <cmd_error>)
    at ./debian/build-src/src/eval.c:1356
#11 0x000056552f7500f0 in command_loop_2 (ignore=ignore@entry=0x0) at ./debian/build-src/src/keyboard.c:1091
#12 0x000056552f7ccea9 in internal_catch (tag=tag@entry=0xd530, func=func@entry=0x56552f7500c0 <command_loop_2>, arg=arg@entry=0x0) at ./debian/build-src/src/eval.c:1117
#13 0x000056552f75007e in command_loop () at ./debian/build-src/src/keyboard.c:1070
#14 0x000056552f75568a in recursive_edit_1 () at ./debian/build-src/src/keyboard.c:714
#15 0x000056552f7559c9 in Frecursive_edit () at ./debian/build-src/src/keyboard.c:786
#16 0x000056552f66caca in main (argc=2, argv=<optimized out>) at ./debian/build-src/src/emacs.c:2062


---

Reading symbols from emacs...
Reading symbols from /usr/lib/debug/.build-id/96/8bd488365ca5ef23edbd3ff2265fa59c1ed52e.debug...
Attaching to program: /usr/bin/emacs, process 31835
[New LWP 31836]
[New LWP 31837]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pselect64_syscall (sigmask=<optimized out>, timeout=<optimized out>, exceptfds=0x0, writefds=0x7ffdcff6aad0, readfds=0x7ffdcff6aa50, nfds=7) at ../sysdeps/unix/sysv/linux/pselect.c:34
34      ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
(gdb) where
#0  pselect64_syscall (sigmask=<optimized out>, timeout=<optimized out>, exceptfds=0x0, writefds=0x7ffdcff6aad0, readfds=0x7ffdcff6aa50, nfds=7) at ../sysdeps/unix/sysv/linux/pselect.c:34
#1  __pselect (nfds=7, readfds=0x7ffdcff6aa50, writefds=0x7ffdcff6aad0, exceptfds=0x0, timeout=<optimized out>, sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/pselect.c:56
#2  0x000056552f834785 in really_call_select (arg=0x7ffdcff6a960) at ./debian/build-src/src/thread.c:586
#3  0x000056552f83551d in thread_select (func=<optimized out>, max_fds=max_fds@entry=7, rfds=rfds@entry=0x7ffdcff6aa50, wfds=wfds@entry=0x7ffdcff6aad0, efds=efds@entry=0x0,
    timeout=timeout@entry=0x7ffdcff6b070, sigmask=0x0) at ./debian/build-src/src/thread.c:616
#4  0x000056552f85238f in xg_select (fds_lim=7, rfds=rfds@entry=0x7ffdcff6b180, wfds=wfds@entry=0x7ffdcff6b200, efds=efds@entry=0x0, timeout=timeout@entry=0x7ffdcff6b070,
    sigmask=sigmask@entry=0x0) at ./debian/build-src/src/xgselect.c:117
#5  0x000056552f812319 in wait_reading_process_output (time_limit=time_limit@entry=30, nsecs=nsecs@entry=0, read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true,
    wait_for_cell=wait_for_cell@entry=0x0, wait_proc=wait_proc@entry=0x0, just_wait_proc=0) at ./debian/build-src/src/process.c:5571
#6  0x000056552f676d53 in sit_for (timeout=timeout@entry=0x7a, reading=reading@entry=true, display_option=display_option@entry=1) at ./debian/build-src/src/dispnew.c:6056
#7  0x000056552f75d494 in read_char (commandflag=1, map=0x5655312ca9d3, prev_event=0x0, used_mouse_menu=0x7ffdcff6ba4b, end_time=0x0) at ./debian/build-src/src/keyboard.c:2738
#8  0x000056552f75db6a in read_key_sequence (keybuf=<optimized out>, prompt=0x0, dont_downcase_last=<optimized out>, can_return_switch_frame=true, fix_current_buffer=true,
    prevent_redisplay=<optimized out>) at ./debian/build-src/src/keyboard.c:9553
#9  0x000056552f75f30c in command_loop_1 () at ./debian/build-src/src/keyboard.c:1350
#10 0x000056552f7ccf67 in internal_condition_case (bfun=bfun@entry=0x56552f75f110 <command_loop_1>, handlers=handlers@entry=0x90, hfun=hfun@entry=0x56552f755a80 <cmd_error>)
    at ./debian/build-src/src/eval.c:1356
#11 0x000056552f7500f0 in command_loop_2 (ignore=ignore@entry=0x0) at ./debian/build-src/src/keyboard.c:1091
#12 0x000056552f7ccea9 in internal_catch (tag=tag@entry=0xd530, func=func@entry=0x56552f7500c0 <command_loop_2>, arg=arg@entry=0x0) at ./debian/build-src/src/eval.c:1117
#13 0x000056552f75007e in command_loop () at ./debian/build-src/src/keyboard.c:1070
#14 0x000056552f75568a in recursive_edit_1 () at ./debian/build-src/src/keyboard.c:714
#15 0x000056552f7559c9 in Frecursive_edit () at ./debian/build-src/src/keyboard.c:786
#16 0x000056552f66caca in main (argc=2, argv=<optimized out>) at ./debian/build-src/src/emacs.c:2062

[-- Attachment #2: Type: text/html, Size: 14401 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-07 20:33 bug#65811: 27.1; zzzzzzzz forever Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  7:39   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
                     ` (2 more replies)
  2023-09-08  5:47 ` Eli Zaretskii
  1 sibling, 3 replies; 14+ messages in thread
From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08  3:19 UTC (permalink / raw)
  To: Bruce Adams; +Cc: 65811-done

This is a problem many users have reported, that arises from a bug
within the WSL X server's treatment of key press and repeat events.
It is not within our power to fix it; use the Cygwin or MS Windows
builds instead.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-07 20:33 bug#65811: 27.1; zzzzzzzz forever Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08  5:47 ` Eli Zaretskii
  1 sibling, 0 replies; 14+ messages in thread
From: Eli Zaretskii @ 2023-09-08  5:47 UTC (permalink / raw)
  To: Bruce Adams; +Cc: 65811

> Date: Thu, 7 Sep 2023 20:33:31 +0000
> From:  Bruce Adams via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> This bug report concerns issue one which is that sometimes
> my emacs inexplicably starts filling with repeated zzzzzzz characters.
> Though other editing activity is possible inbetween 'attacks'
> 
> This continues even if I unplug the keyboard (to rule out a USB keyboard
> issue).zzzzzzzzzzzzzzzzzzzzzzz
> It is possible to get control back temporarily by changing the window
> size.zzzzzzzzzzzzzz
> The added zzzzz... can be undone using ctrl-u.

When this happens, type "C-h l" and see if Emacs really got those 'z'
characters in its input.  If it did, there's nothing Emacs can do
about it: the OS somehow stuffs those characters into the Emacs input
queue.

> My second issue is that if left running (typically unattended or out of
> focus) for a long time emacs crashes. I will try to add a second bug report
> with a backtrace when this happens.
> I did not have the debug symbols installed for previous occurances but
> it is quite repeatable.

Yes, please, we need backtraces from GDB to try to understand what
could cause these crashes.

> I have a couple of backtraces below for the zzzz issue:

Those backtraces just say that Emacs is idle waiting for input.  They
give no hint about the problem, which is expected if the problem is
outside of Emacs.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08  7:39   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  7:56   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 12:37   ` Eli Zaretskii
  2 siblings, 0 replies; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08  7:39 UTC (permalink / raw)
  To: Po Lu; +Cc: 65811-done@debbugs.gnu.org

Thanks that is useful to know. Do you have a link to a bug report of this to MS? 
I see I can get there via using local paths like //wsl.localhost/Ubuntu-22.04/home/user/ so at least there is a workaround.

Regards,

Bruce.

-----Original Message-----
From: Po Lu <luangruo@yahoo.com> 
Sent: Friday, September 8, 2023 4:19 AM
To: Bruce Adams <bruce@optibrium.com>
Cc: 65811-done@debbugs.gnu.org
Subject: Re: bug#65811: 27.1; zzzzzzzz forever

This is a problem many users have reported, that arises from a bug within the WSL X server's treatment of key press and repeat events.
It is not within our power to fix it; use the Cygwin or MS Windows builds instead.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  7:39   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08  7:56   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 11:49     ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 12:37   ` Eli Zaretskii
  2 siblings, 1 reply; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08  7:56 UTC (permalink / raw)
  To: 65811-done@debbugs.gnu.org

I think it may be this one -
 https://github.com/microsoft/wslg/issues/207

see also https://stackoverflow.com/questions/74932957/x11-sending-wrong-key-presses

-----Original Message-----
From: Po Lu <luangruo@yahoo.com> 
Sent: Friday, September 8, 2023 4:19 AM
To: Bruce Adams <bruce@optibrium.com>
Cc: 65811-done@debbugs.gnu.org
Subject: Re: bug#65811: 27.1; zzzzzzzz forever

This is a problem many users have reported, that arises from a bug within the WSL X server's treatment of key press and repeat events.
It is not within our power to fix it; use the Cygwin or MS Windows builds instead.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08  7:56   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08 11:49     ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 13:14       ` Eli Zaretskii
  0 siblings, 1 reply; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08 11:49 UTC (permalink / raw)
  To: 65811-done@debbugs.gnu.org

Actually the workaround of using Cygwin does not quite work. I get issues with this saving files:

■  Warning (unlock-file): Unlocking file: Invalid argument, //wsl.localhost/Ubuntu-22.04/home/brucea/foobar, ignored

-----Original Message-----
From: Bruce Adams 
Sent: Friday, September 8, 2023 8:56 AM
To: 65811-done@debbugs.gnu.org
Subject: RE: bug#65811: 27.1; zzzzzzzz forever

I think it may be this one -
 https://github.com/microsoft/wslg/issues/207

see also https://stackoverflow.com/questions/74932957/x11-sending-wrong-key-presses

-----Original Message-----
From: Po Lu <luangruo@yahoo.com> 
Sent: Friday, September 8, 2023 4:19 AM
To: Bruce Adams <bruce@optibrium.com>
Cc: 65811-done@debbugs.gnu.org
Subject: Re: bug#65811: 27.1; zzzzzzzz forever

This is a problem many users have reported, that arises from a bug within the WSL X server's treatment of key press and repeat events.
It is not within our power to fix it; use the Cygwin or MS Windows builds instead.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  7:39   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08  7:56   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08 12:37   ` Eli Zaretskii
  2 siblings, 0 replies; 14+ messages in thread
From: Eli Zaretskii @ 2023-09-08 12:37 UTC (permalink / raw)
  To: Po Lu; +Cc: luangruo, bruce, 65811

> Resent-To: bug-gnu-emacs@gnu.org
> Cc: 65811-done@debbugs.gnu.org
> Date: Fri, 08 Sep 2023 11:19:09 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> This is a problem many users have reported, that arises from a bug
> within the WSL X server's treatment of key press and repeat events.
> It is not within our power to fix it; use the Cygwin or MS Windows
> builds instead.

Thanks, I've now added this to PROBLEMS.

I leave the bug open in case we will get the backtraces needed for
investigating the other issue reported here: crashes.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 11:49     ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08 13:14       ` Eli Zaretskii
  2023-09-08 15:02         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  0 siblings, 2 replies; 14+ messages in thread
From: Eli Zaretskii @ 2023-09-08 13:14 UTC (permalink / raw)
  To: Bruce Adams, Ken Brown; +Cc: 65811

> Date: Fri, 8 Sep 2023 11:49:54 +0000
> From:  Bruce Adams via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Actually the workaround of using Cygwin does not quite work. I get issues with this saving files:
> 
> ■  Warning (unlock-file): Unlocking file: Invalid argument, //wsl.localhost/Ubuntu-22.04/home/brucea/foobar, ignored

That's just a warning, and you can turn it off if you want.

Maybe Ken (CCed) could help out with the Cygwin issue of file-locking.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 13:14       ` Eli Zaretskii
@ 2023-09-08 15:02         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-09  1:01           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  1 sibling, 1 reply; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08 15:02 UTC (permalink / raw)
  To: Eli Zaretskii, Ken Brown; +Cc: 65811@debbugs.gnu.org

It was irritating enough to make me switch to the windows native install as rather than just coming up in the warnings window/tile
It replaces the window/tile with the file I'm editing with the warnings tile. I think that may be a lesser bug as well.

In >20 years of using emacs I never had a problem until WSL came along.

-----Original Message-----
From: Eli Zaretskii <eliz@gnu.org> 
Sent: Friday, September 8, 2023 2:15 PM
To: Bruce Adams <bruce@optibrium.com>; Ken Brown <kbrown@cornell.edu>
Cc: 65811@debbugs.gnu.org
Subject: Re: bug#65811: 27.1; zzzzzzzz forever

> Date: Fri, 8 Sep 2023 11:49:54 +0000
> From:  Bruce Adams via "Bug reports for GNU Emacs,  the Swiss army 
> knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Actually the workaround of using Cygwin does not quite work. I get issues with this saving files:
> 
> ■  Warning (unlock-file): Unlocking file: Invalid argument, 
> //wsl.localhost/Ubuntu-22.04/home/brucea/foobar, ignored

That's just a warning, and you can turn it off if you want.

Maybe Ken (CCed) could help out with the Cygwin issue of file-locking.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 13:14       ` Eli Zaretskii
  2023-09-08 15:02         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 15:30           ` Eli Zaretskii
  2023-09-09  1:00           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  1 sibling, 2 replies; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08 15:10 UTC (permalink / raw)
  To: Eli Zaretskii, Ken Brown; +Cc: 65811@debbugs.gnu.org

I have a backtrace here:

apt-get changelog emacs
Get:1 https://changelogs.ubuntu.com emacs 1:27.1+1-3ubuntu5.1 Changelog [113 kB]
Fetched 113 kB in 1s (157 kB/s)
brucea@Bruce-PC-23:~/work/git/ubuntu-servers$ Connection lost to X server ':0'
When compiled with GTK, Emacs cannot recover from X disconnects.
This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
For details, see etc/PROBLEMS.
Backtrace:
emacs(+0x150e55)[0x55b8db8bde55]
emacs(+0x4aa38)[0x55b8db7b7a38]
emacs(+0x4af4f)[0x55b8db7b7f4f]
emacs(+0x49f22)[0x55b8db7b6f22]
emacs(+0x49ff3)[0x55b8db7b6ff3]
/lib/x86_64-linux-gnu/libX11.so.6(_XIOError+0x63)[0x7f076d2c82f3]
/lib/x86_64-linux-gnu/libX11.so.6(_XReply+0x3ef)[0x7f076d2cd56f]
/lib/x86_64-linux-gnu/libX11.so.6(XGetWindowProperty+0x108)[0x7f076d2ac568]
/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x781f9)[0x7f076da6a1f9]
/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7830e)[0x7f076da6a30e]
/lib/x86_64-linux-gnu/libgdk-3.so.0(gdk_x11_screen_supports_net_wm_hint+0x8c)[0x7f076da6b4dc]
/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7fb4f)[0x7f076da71b4f]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x1290)[0x7f076d55b700]
/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7f076d55b863]
/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x46966)[0x7f076da38966]
/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x332ad)[0x7f076da252ad]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x562c8)[0x7f076d4452c8]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x174)[0x7f076d444c44]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xab258)[0x7f076d49a258]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x33)[0x7f076d4423e3]
/lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main_iteration+0x19)[0x7f076dd43d99]
emacs(+0x104fd3)[0x55b8db871fd3]
emacs(+0x13d3e2)[0x55b8db8aa3e2]
emacs(+0x13d9d5)[0x55b8db8aa9d5]
emacs(+0x1f8c95)[0x55b8db965c95]
emacs(+0x14158f)[0x55b8db8ae58f]
emacs(+0x143b6a)[0x55b8db8b0b6a]
emacs(+0x14530c)[0x55b8db8b230c]
emacs(+0x1b2f67)[0x55b8db91ff67]
emacs(+0x1360f0)[0x55b8db8a30f0]
emacs(+0x1b2ea9)[0x55b8db91fea9]
emacs(+0x13607e)[0x55b8db8a307e]
emacs(+0x13b68a)[0x55b8db8a868a]
emacs(+0x13b9c9)[0x55b8db8a89c9]
emacs(+0x52aca)[0x55b8db7bfaca]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f076bc56d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f076bc56e40]
emacs(+0x531b5)[0x55b8db7c01b5]

[1]+  Aborted                 emacs

-----Original Message-----
From: Eli Zaretskii <eliz@gnu.org> 
Sent: Friday, September 8, 2023 2:15 PM
To: Bruce Adams <bruce@optibrium.com>; Ken Brown <kbrown@cornell.edu>
Cc: 65811@debbugs.gnu.org
Subject: Re: bug#65811: 27.1; zzzzzzzz forever

> Date: Fri, 8 Sep 2023 11:49:54 +0000
> From:  Bruce Adams via "Bug reports for GNU Emacs,  the Swiss army 
> knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Actually the workaround of using Cygwin does not quite work. I get issues with this saving files:
> 
> ■  Warning (unlock-file): Unlocking file: Invalid argument, 
> //wsl.localhost/Ubuntu-22.04/home/brucea/foobar, ignored

That's just a warning, and you can turn it off if you want.

Maybe Ken (CCed) could help out with the Cygwin issue of file-locking.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-08 15:30           ` Eli Zaretskii
  2023-09-08 19:54             ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-09  1:00           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  1 sibling, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2023-09-08 15:30 UTC (permalink / raw)
  To: Bruce Adams; +Cc: 65811, kbrown

> From: Bruce Adams <bruce@optibrium.com>
> CC: "65811@debbugs.gnu.org" <65811@debbugs.gnu.org>
> Date: Fri, 8 Sep 2023 15:10:06 +0000
> 
> I have a backtrace here:
> 
> apt-get changelog emacs
> Get:1 https://changelogs.ubuntu.com emacs 1:27.1+1-3ubuntu5.1 Changelog [113 kB]
> Fetched 113 kB in 1s (157 kB/s)
> brucea@Bruce-PC-23:~/work/git/ubuntu-servers$ Connection lost to X server ':0'
> When compiled with GTK, Emacs cannot recover from X disconnects.
> This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
> For details, see etc/PROBLEMS.
> Backtrace:
> emacs(+0x150e55)[0x55b8db8bde55]
> emacs(+0x4aa38)[0x55b8db7b7a38]
> emacs(+0x4af4f)[0x55b8db7b7f4f]
> emacs(+0x49f22)[0x55b8db7b6f22]
> emacs(+0x49ff3)[0x55b8db7b6ff3]
> /lib/x86_64-linux-gnu/libX11.so.6(_XIOError+0x63)[0x7f076d2c82f3]
> /lib/x86_64-linux-gnu/libX11.so.6(_XReply+0x3ef)[0x7f076d2cd56f]
> /lib/x86_64-linux-gnu/libX11.so.6(XGetWindowProperty+0x108)[0x7f076d2ac568]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x781f9)[0x7f076da6a1f9]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7830e)[0x7f076da6a30e]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(gdk_x11_screen_supports_net_wm_hint+0x8c)[0x7f076da6b4dc]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7fb4f)[0x7f076da71b4f]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x1290)[0x7f076d55b700]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7f076d55b863]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x46966)[0x7f076da38966]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x332ad)[0x7f076da252ad]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x562c8)[0x7f076d4452c8]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x174)[0x7f076d444c44]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xab258)[0x7f076d49a258]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x33)[0x7f076d4423e3]
> /lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main_iteration+0x19)[0x7f076dd43d99]
> emacs(+0x104fd3)[0x55b8db871fd3]
> emacs(+0x13d3e2)[0x55b8db8aa3e2]
> emacs(+0x13d9d5)[0x55b8db8aa9d5]
> emacs(+0x1f8c95)[0x55b8db965c95]
> emacs(+0x14158f)[0x55b8db8ae58f]
> emacs(+0x143b6a)[0x55b8db8b0b6a]
> emacs(+0x14530c)[0x55b8db8b230c]
> emacs(+0x1b2f67)[0x55b8db91ff67]
> emacs(+0x1360f0)[0x55b8db8a30f0]
> emacs(+0x1b2ea9)[0x55b8db91fea9]
> emacs(+0x13607e)[0x55b8db8a307e]
> emacs(+0x13b68a)[0x55b8db8a868a]
> emacs(+0x13b9c9)[0x55b8db8a89c9]
> emacs(+0x52aca)[0x55b8db7bfaca]
> /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f076bc56d90]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f076bc56e40]
> emacs(+0x531b5)[0x55b8db7c01b5]
> 
> [1]+  Aborted                 emacs

Thanks, but those addresses can only be interpreted on your machine.
So either use the method described in the node "Crashing" of the Emacs
user manual, or (better) run Emacs under GDB, and when it crashes and
GDB gets control, type at the GDB prompt:

  (gdb) thread apply all bt

and post here everything that GDB shows in response.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 15:30           ` Eli Zaretskii
@ 2023-09-08 19:54             ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  0 siblings, 0 replies; 14+ messages in thread
From: Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-08 19:54 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 65811@debbugs.gnu.org, kbrown@cornell.edu

Here is another instance of the idle crash with full backtrace.
By "idle crash" I mean I was AFK for a few hours and came back and there was a SIGABRT.

gdb) cont
Continuing.
[Detaching after vfork from child process 24730]
[Detaching after vfork from child process 24731]
[Detaching after vfork from child process 25402]
[Detaching after vfork from child process 25403]
[Detaching after vfork from child process 25454]
[Detaching after vfork from child process 25455]
[Detaching after vfork from child process 25456]

Thread 1 "emacs" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140210052194304) at ./nptl/pthread_kill.c:44
44      ./nptl/pthread_kill.c: No such file or directory.
(gdb) thread apply all bt

Thread 7 (Thread 0x7f8519ffb640 (LWP 23561) "dconf worker"):
#0  0x00007f853544ad7f in __GI___poll (fds=0x5604b7104350, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f8536b9f1f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8536b473e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f85305f733d in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4  0x00007f8536b78a51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f85353c6b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#6  0x00007f8535458a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 6 (Thread 0x7f851a7fc640 (LWP 23560) "emacs"):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f8514000b98, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007f85353c5ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5604b6f37d50, cond=0x7f8514000b70) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x7f8514000b70, mutex=0x5604b6f37d50) at ./nptl/pthread_cond_wait.c:627
#5  0x00007f8530ae1caf in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#6  0x00007f8530dbc7bb in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#7  0x00007f8530dbcd6b in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#8  0x00007f85353c6b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#9  0x00007f8535458a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 5 (Thread 0x7f851affd640 (LWP 23559) "emacs"):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f8514000b98, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007f85353c5ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5604b6f37d50, cond=0x7f8514000b70) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x7f8514000b70, mutex=0x5604b6f37d50) at ./nptl/pthread_cond_wait.c:627
#5  0x00007f8530ae1caf in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#6  0x00007f8530dbc7bb in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#7  0x00007f8530dbcd6b in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#8  0x00007f85353c6b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#9  0x00007f8535458a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7f851b7fe640 (LWP 23558) "emacs"):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f8514000b98, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007f85353c5ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5604b6f37d50, cond=0x7f8514000b70) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x7f8514000b70, mutex=0x5604b6f37d50) at ./nptl/pthread_cond_wait.c:627
#5  0x00007f8530ae1caf in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#6  0x00007f8530dbc7bb in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#7  0x00007f8530dbcd6b in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#8  0x00007f85353c6b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#9  0x00007f8535458a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
--Type <RET> for more, q to quit, c to continue without paging--

Thread 3 (Thread 0x7f851bfff640 (LWP 23557) "emacs"):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f8514000b98) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f8514000b98, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3  0x00007f85353c5ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5604b6f37d50, cond=0x7f8514000b70) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x7f8514000b70, mutex=0x5604b6f37d50) at ./nptl/pthread_cond_wait.c:627
#5  0x00007f8530ae1caf in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#6  0x00007f8530dbc7bb in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#7  0x00007f8530dbcd6b in ?? () from /usr/lib/wsl/lib/libd3d12core.so
#8  0x00007f85353c6b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#9  0x00007f8535458a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 2 (Thread 0x7f8531b1c640 (LWP 23556) "gmain"):
#0  0x00007f853544ad7f in __GI___poll (fds=0x5604b6ba9930, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f8536b9f1f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8536b473e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8536b47431 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f8536b78a51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f85353c6b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#6  0x00007f8535458a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 1 (Thread 0x7f85325ae000 (LWP 23555) "emacs"):
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140210052194304) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140210052194304) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140210052194304, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007f8535374476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00005604b4c5ba65 in terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=40) at ./debian/build-src/src/emacs.c:409
#5  0x00005604b4c5bf4f in emacs_abort () at ./debian/build-src/src/sysdep.c:2461
#6  0x00005604b4c58e0c in redisplay_internal () at ./debian/build-src/src/xdisp.c:15298
#7  0x00005604b4ca70d6 in redisplay_preserve_echo_area (from_where=from_where@entry=13) at ./debian/build-src/src/xdisp.c:16111
#8  0x00005604b4e04868 in Fdelete_process (process=0x5604b6d1f175) at ./debian/build-src/src/process.c:1095
#9  0x00005604b4e0c525 in kill_buffer_processes (buffer=buffer@entry=0x0) at ./debian/build-src/src/process.c:8050
#10 0x00005604b4d46a9a in shut_down_emacs (sig=0, stuff=0x0) at ./debian/build-src/src/emacs.c:2465
#11 0x00005604b4c5aefc in x_connection_closed (dpy=dpy@entry=0x5604b6df6e90, error_message=error_message@entry=0x7fffb2d49d28 "Connection lost to X server ':0'", ioerror=ioerror@entry=true) at ./debian/build-src/src/xterm.c:10058
#12 0x00005604b4c5aff3 in x_io_error_quitter (display=0x5604b6df6e90) at ./debian/build-src/src/xterm.c:10161
#13 0x00007f85369cd2f3 in _XIOError () from /lib/x86_64-linux-gnu/libX11.so.6
#14 0x00007f85369d256f in _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
#15 0x00007f85369b1568 in XGetWindowProperty () from /lib/x86_64-linux-gnu/libX11.so.6
#16 0x00007f853716f1f9 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#17 0x00007f853716f30e in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#18 0x00007f85371704dc in gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#19 0x00007f8537176b4f in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#20 0x00007f8536c60700 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007f8536c60863 in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007f853713d966 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
--Type <RET> for more, q to quit, c to continue without paging--
#23 0x00007f853712a2ad in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#24 0x00007f8536b4a2c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f8536b49c44 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f8536b9f258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f8536b473e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f8537448d99 in gtk_main_iteration () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#29 0x00005604b4d15fd3 in XTread_socket (terminal=<optimized out>, hold_quit=0x7fffb2d4a520) at ./debian/build-src/src/xterm.c:9382
#30 0x00005604b4d4e3e2 in gobble_input () at ./debian/build-src/src/keyboard.c:6891
#31 0x00005604b4d4e9d5 in handle_async_input () at ./debian/build-src/src/keyboard.c:7128
#32 process_pending_signals () at ./debian/build-src/src/keyboard.c:7142
#33 0x00005604b4e09c95 in wait_reading_process_output (time_limit=time_limit@entry=0, nsecs=nsecs@entry=0, read_kbd=read_kbd@entry=-1, do_display=true, wait_for_cell=wait_for_cell@entry=0x0, wait_proc=wait_proc@entry=0x0, just_wait_proc=0) at ./debian/build-src/src/process.c:5250
#34 0x00005604b4d5258f in kbd_buffer_get_event (end_time=0x0, used_mouse_menu=0x7fffb2d4b02b, kbp=<synthetic pointer>) at ./debian/build-src/src/keyboard.c:3866
#35 read_event_from_main_queue (used_mouse_menu=0x7fffb2d4b02b, local_getcjmp=0x7fffb2d4ac30, end_time=0x0) at ./debian/build-src/src/keyboard.c:2156
#36 read_decoded_event_from_main_queue (used_mouse_menu=<optimized out>, prev_event=<optimized out>, local_getcjmp=<optimized out>, end_time=<optimized out>) at ./debian/build-src/src/keyboard.c:2220
#37 read_char (commandflag=1, map=0x5604b7e61683, prev_event=0x0, used_mouse_menu=0x7fffb2d4b02b, end_time=0x0) at ./debian/build-src/src/keyboard.c:2830
#38 0x00005604b4d54b6a in read_key_sequence (keybuf=<optimized out>, prompt=0x0, dont_downcase_last=<optimized out>, can_return_switch_frame=true, fix_current_buffer=true, prevent_redisplay=<optimized out>) at ./debian/build-src/src/keyboard.c:9553
#39 0x00005604b4d5630c in command_loop_1 () at ./debian/build-src/src/keyboard.c:1350
#40 0x00005604b4dc3f67 in internal_condition_case (bfun=bfun@entry=0x5604b4d56110 <command_loop_1>, handlers=handlers@entry=0x90, hfun=hfun@entry=0x5604b4d4ca80 <cmd_error>) at ./debian/build-src/src/eval.c:1356
#41 0x00005604b4d470f0 in command_loop_2 (ignore=ignore@entry=0x0) at ./debian/build-src/src/keyboard.c:1091
#42 0x00005604b4dc3ea9 in internal_catch (tag=tag@entry=0xd530, func=func@entry=0x5604b4d470c0 <command_loop_2>, arg=arg@entry=0x0) at ./debian/build-src/src/eval.c:1117
#43 0x00005604b4d4707e in command_loop () at ./debian/build-src/src/keyboard.c:1070
#44 0x00005604b4d4c68a in recursive_edit_1 () at ./debian/build-src/src/keyboard.c:714
#45 0x00005604b4d4c9c9 in Frecursive_edit () at ./debian/build-src/src/keyboard.c:786
#46 0x00005604b4c63aca in main (argc=1, argv=<optimized out>) at ./debian/build-src/src/emacs.c:2062

-----Original Message-----
From: Eli Zaretskii <eliz@gnu.org> 
Sent: Friday, September 8, 2023 4:31 PM
To: Bruce Adams <bruce@optibrium.com>
Cc: kbrown@cornell.edu; 65811@debbugs.gnu.org
Subject: Re: bug#65811: 27.1; zzzzzzzz forever

> From: Bruce Adams <bruce@optibrium.com>
> CC: "65811@debbugs.gnu.org" <65811@debbugs.gnu.org>
> Date: Fri, 8 Sep 2023 15:10:06 +0000
> 
> I have a backtrace here:
> 
> apt-get changelog emacs
> Get:1 https://changelogs.ubuntu.com emacs 1:27.1+1-3ubuntu5.1 
> Changelog [113 kB] Fetched 113 kB in 1s (157 kB/s) 
> brucea@Bruce-PC-23:~/work/git/ubuntu-servers$ Connection lost to X server ':0'
> When compiled with GTK, Emacs cannot recover from X disconnects.
> This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
> For details, see etc/PROBLEMS.
> Backtrace:
> emacs(+0x150e55)[0x55b8db8bde55]
> emacs(+0x4aa38)[0x55b8db7b7a38]
> emacs(+0x4af4f)[0x55b8db7b7f4f]
> emacs(+0x49f22)[0x55b8db7b6f22]
> emacs(+0x49ff3)[0x55b8db7b6ff3]
> /lib/x86_64-linux-gnu/libX11.so.6(_XIOError+0x63)[0x7f076d2c82f3]
> /lib/x86_64-linux-gnu/libX11.so.6(_XReply+0x3ef)[0x7f076d2cd56f]
> /lib/x86_64-linux-gnu/libX11.so.6(XGetWindowProperty+0x108)[0x7f076d2a
> c568] /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x781f9)[0x7f076da6a1f9]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7830e)[0x7f076da6a30e]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(gdk_x11_screen_supports_net_wm_hin
> t+0x8c)[0x7f076da6b4dc] 
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7fb4f)[0x7f076da71b4f]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x1290)
> [0x7f076d55b700] 
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7f076d
> 55b863] /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x46966)[0x7f076da38966]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x332ad)[0x7f076da252ad]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x562c8)[0x7f076d4452c8]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x174)[
> 0x7f076d444c44] 
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xab258)[0x7f076d49a258]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x33)[
> 0x7f076d4423e3] 
> /lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main_iteration+0x19)[0x7f076dd
> 43d99]
> emacs(+0x104fd3)[0x55b8db871fd3]
> emacs(+0x13d3e2)[0x55b8db8aa3e2]
> emacs(+0x13d9d5)[0x55b8db8aa9d5]
> emacs(+0x1f8c95)[0x55b8db965c95]
> emacs(+0x14158f)[0x55b8db8ae58f]
> emacs(+0x143b6a)[0x55b8db8b0b6a]
> emacs(+0x14530c)[0x55b8db8b230c]
> emacs(+0x1b2f67)[0x55b8db91ff67]
> emacs(+0x1360f0)[0x55b8db8a30f0]
> emacs(+0x1b2ea9)[0x55b8db91fea9]
> emacs(+0x13607e)[0x55b8db8a307e]
> emacs(+0x13b68a)[0x55b8db8a868a]
> emacs(+0x13b9c9)[0x55b8db8a89c9]
> emacs(+0x52aca)[0x55b8db7bfaca]
> /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f076bc56d90]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f076bc56e40
> ]
> emacs(+0x531b5)[0x55b8db7c01b5]
> 
> [1]+  Aborted                 emacs

Thanks, but those addresses can only be interpreted on your machine.
So either use the method described in the node "Crashing" of the Emacs user manual, or (better) run Emacs under GDB, and when it crashes and GDB gets control, type at the GDB prompt:

  (gdb) thread apply all bt

and post here everything that GDB shows in response.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-09-08 15:30           ` Eli Zaretskii
@ 2023-09-09  1:00           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  1 sibling, 0 replies; 14+ messages in thread
From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-09  1:00 UTC (permalink / raw)
  To: Bruce Adams; +Cc: Eli Zaretskii, 65811@debbugs.gnu.org, Ken Brown

Bruce Adams <bruce@optibrium.com> writes:

> I have a backtrace here:
>
> apt-get changelog emacs
> Get:1 https://changelogs.ubuntu.com emacs 1:27.1+1-3ubuntu5.1 Changelog [113 kB]
> Fetched 113 kB in 1s (157 kB/s)
> brucea@Bruce-PC-23:~/work/git/ubuntu-servers$ Connection lost to X server ':0'
> When compiled with GTK, Emacs cannot recover from X disconnects.
> This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221

This is no Emacs bug.  Your X server crashed, and Emacs is merely
aborting to inform you that GTK builds are incapable of recovering from
the subsequent server disconnect.





^ permalink raw reply	[flat|nested] 14+ messages in thread

* bug#65811: 27.1; zzzzzzzz forever
  2023-09-08 15:02         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-09-09  1:01           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  0 siblings, 0 replies; 14+ messages in thread
From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-09-09  1:01 UTC (permalink / raw)
  To: Bruce Adams; +Cc: Eli Zaretskii, 65811@debbugs.gnu.org, Ken Brown

Bruce Adams <bruce@optibrium.com> writes:

> In >20 years of using emacs I never had a problem until WSL came along.

Another reason not to use Weasel, I suppose..?





^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2023-09-09  1:01 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-09-07 20:33 bug#65811: 27.1; zzzzzzzz forever Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08  7:39   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08  7:56   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 11:49     ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 13:14       ` Eli Zaretskii
2023-09-08 15:02         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09  1:01           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:30           ` Eli Zaretskii
2023-09-08 19:54             ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09  1:00           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 12:37   ` Eli Zaretskii
2023-09-08  5:47 ` Eli Zaretskii

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).