GNOME Bugzilla – Bug 784834
Crash of gnome-shell with TRAP (Connection to xwayland lost)
Last modified: 2017-07-12 10:24:29 UTC
GDM terminated with a TRAP in GNOME Shell 3.22.3 (package *gnome-shell* 3.22.3-3 in Debian Sid/unstable). ``` $ sudo coredumpctl info 1589 PID: 1589 (gnome-shell) UID: 130 (Debian-gdm) GID: 141 (Debian-gdm) Signal: 5 (TRAP) Timestamp: Wed 2017-07-12 09:33:12 CEST (23min ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-130.slice/session-c1.scope Unit: session-c1.scope Slice: user-130.slice Session: c1 Owner UID: 130 (Debian-gdm) Boot ID: 9ce25702e4ce42d4b198b5fbd175a01f Machine ID: 1572dc2ca76ca04c3351599547f539a6 Hostname: myasrocke350m1 Storage: /var/lib/systemd/coredump/core.gnome-shell.130.9ce25702e4ce42d4b198b5fbd175a01f.1589.1499844792000000.lz4 Message: Process 1589 (gnome-shell) of user 130 dumped core. Stack trace of thread 1589: #0 0x00000000b6348040 _g_log_abort (libglib-2.0.so.0) #1 0x00000000b6348fba g_log_default_handler (libglib-2.0.so.0) #2 0x0000000080056002 n/a (gnome-shell) #3 0x00000000b6349224 g_logv (libglib-2.0.so.0) #4 0x00000000b63493f5 g_log (libglib-2.0.so.0) #5 0x00000000b70aa4b4 n/a (libmutter.so.0) #6 0x00000000b5a0fc3d _XIOError (libX11.so.6) #7 0x00000000b5a0d276 _XEventsQueued (libX11.so.6) #8 0x00000000b59fe762 XPending (libX11.so.6) #9 0x00000000b5920f1b gdk_check_xpending (libgdk-3.so.0) #10 0x00000000b63422aa g_main_context_check (libglib-2.0.so.0) #11 0x00000000b63428b1 g_main_context_iterate (libglib-2.0.so.0) #12 0x00000000b6342d39 g_main_loop_run (libglib-2.0.so.0) #13 0x00000000b7079bef meta_run (libmutter.so.0) #14 0x0000000080055bfc main (gnome-shell) #15 0x00000000b613f276 __libc_start_main (libc.so.6) #16 0x0000000080055d4b n/a (gnome-shell) ```
Here is the trace retrieved with `sudo coredumpctl gdb 1589`.
+ Trace 237638
Here is the full backtrace.
+ Trace 237639
Thread 1 (Thread 0xb1c6a940 (LWP 1589))
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 759538 ***
(In reply to Florian Müllner from comment #3) > Thanks for taking the time to report this. > This particular bug has already been reported into our bug tracking system, > but please feel free to report any further bugs you find. > > *** This bug has been marked as a duplicate of bug 759538 *** Are you sure about that? I see this crash in gnome-shell quite often, and I _do_ have X installed.
It's not about whether X is installed or not:
+ Trace 237640
indicates that XWayland is crashing. As currently core functionality in mutter is based on X11 (even on wayland), this is a fatal error.
(In reply to Florian Müllner from comment #5) > It's not about whether X is installed or not: Exactly. But you marked this bug report as a duplicate of bug #759538, which is about the fact that gnome-shell requires X to be installed, am I wrong?
No, it's about mutter requiring XWayland even when all open applications are using the wayland backend. That's because mutter *itself* depends on XWayland, so unless that core reliance on X11 is removed, x crash of the X server will be fatal.
Or putting it in more practical terms: There is no quick fix for this on the mutter/gnome-shell side. If you are looking for a short-term fix, focusing on the Xwayland crash is your best bet.
Ok, thanks for the clarification!