GNOME Bugzilla – Bug 742508
wayland: gnome session crashes abruptly
Last modified: 2021-07-05 14:29:08 UTC
I was playing on my terminal, gnome session on wayland crashed abruptly and took me to login screen again. Upon inspection, I am here with following stack trace that I got from journalctl. ----------------------------------------------------------------- Jan 07 12:32:36 h3xor gnome-session[3966]: Window manager warning: last_user_time (1349488) is greater than comparison timestamp (1349485). This most Jan 07 12:32:36 h3xor gnome-session[3966]: Window manager warning: 0x1800007 (pranavk@h3) appears to be one of the offending windows with a timestamp Jan 07 12:32:36 h3xor gnome-session[3966]: Window manager warning: last_user_time (1350043) is greater than comparison timestamp (1350042). This most Jan 07 12:32:36 h3xor gnome-session[3966]: Window manager warning: 0x1800007 (pranavk@h3) appears to be one of the offending windows with a timestamp Jan 07 12:32:36 h3xor gnome-session[3966]: Window manager warning: last_user_time (1350074) is greater than comparison timestamp (1350072). This most Jan 07 12:32:36 h3xor gnome-session[3966]: Window manager warning: 0x1800007 (pranavk@h3) appears to be one of the offending windows with a timestamp Jan 07 12:32:43 h3xor gnome-session[3966]: 1420614163383 GMPInstallManager.simpleCheckAndInstall INFO Auto-update is off for open Jan 07 12:32:53 h3xor systemd-coredump[3676]: Process 1958 (gnome-shell) of user 1000 dumped core. Stack trace of thread 1958: #0 0x00007f81d7821c60 g_logv (libglib-2.0.so.0) #1 0x00007f81d7821e9f g_log (libglib-2.0.so.0) #2 0x00007f81db33ab9e x_io_error (libmutter.so.0) #3 0x00007f81d623d57e _XIOError (libX11.so.6) #4 0x00007f81d623aebd _XEventsQueued (libX11.so.6) #5 0x00007f81d622c7d7 XPending (libX11.so.6) #6 0x00007f81d893db4c gdk_event_source_check (libgdk-3.so.0) #7 0x00007f81d781a841 g_main_context_check (libglib-2.0.so.0) #8 0x00007f81d781adc3 g_main_context_iterate.isra.29 (libglib-2.0.so.0) #9 0x00007f81d781b1b2 g_main_loop_run (libglib-2.0.so.0) #10 0x00007f81db2fc938 meta_run (libmutter.so.0) #11 0x00000000004023dd main (gnome-shell) #12 0x00007f81d5c3efe0 __libc_start_main (libc.so.6) #13 0x00000000004024e5 _start (gnome-shell) Stack trace of thread 1961: #0 0x00007f81d785cf10 g_variant_type_peek_string (libglib-2.0.so.0) #1 0x00007f81d8c782ca parse_value_from_blob (libgio-2.0.so.0) #2 0x00007f81d8c7a8cb g_dbus_message_new_from_blob (libgio-2.0.so.0) #3 0x00007f81d8c84cd3 _g_dbus_worker_do_read_cb (libgio-2.0.so.0) #4 0x00007f81d8c1a807 g_simple_async_result_complete (libgio-2.0.so.0) #5 0x00007f81d8c1a869 complete_in_idle_cb (libgio-2.0.so.0) #6 0x00007f81d781aaeb g_main_context_dispatch (libglib-2.0.so.0) #7 0x00007f81d781ae88 g_main_context_iterate.isra.29 (libglib-2.0.so.0) #8 0x00007f81d781b1b2 g_main_loop_run (libglib-2.0.so.0) #9 0x00007f81d8c82d96 gdbus_shared_thread_func (libgio-2.0.so.0) #10 0x00007f81d78417b5 g_thread_proxy (libglib-2.0.so.0) #11 0x00007f81d5fe352a start_thread (libpthread.so.0) #12 0x00007f81d5d1f77d __clone (libc.so.6) Stack trace of thread 1960: #0 0x00007f81d5d141dd poll (libc.so.6) #1 0x00007f81d781ae24 g_main_context_iterate.isra.29 (libglib-2.0.so.0) #2 0x00007f81d781af3c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f81d781af79 glib_worker_main (libglib-2.0.so.0) #4 0x00007f81d78417b5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f81d5fe352a start_thread (libpthread.so.0) #6 0x00007f81d5d1f77d __clone (libc.so.6) Stack trace of thread 1985: #0 0x00007f81d5d141dd poll (libc.so.6) #1 0x00007f81d781ae24 g_main_context_iterate.isra.29 (libglib-2.0.so.0) #2 0x00007f81d781af3c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f81c05d324d dconf_gdbus_worker_thread (libdconfsettings.so) #4 0x00007f81d78417b5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007f81d5fe352a start_thread (libpthread.so.0) #6 0x00007f81d5d1f77d __clone (libc.so.6) Stack trace of thread 2018: #0 0x00007f81d5fe8590 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f81d2ac561d PR_WaitCondVar (libnspr4.so) #2 0x00007f81de808bfe _ZN2js22SourceCompressorThread16compressorThreadEPv (libmozjs-24.so) #3 0x00007f81d2acae6b _pt_root (libnspr4.so) #4 0x00007f81d5fe352a start_thread (libpthread.so.0) #5 0x00007f81d5d1f77d __clone (libc.so.6) Stack trace of thread 2016: #0 0x00007f81d5d141dd poll (libc.so.6) #1 0x00007f81d558cfea _xcb_in_read_block (libxcb.so.1) #2 0x00007f81d558afb3 xcb_connect_to_fd (libxcb.so.1) #3 0x00007f81d558e8c1 xcb_connect_to_display_with_auth_info (libxcb.so.1) #4 0x00007f81d59f2f0a pa_client_conf_from_x11 (libpulsecommon-5.0.so) #5 0x00007f81df77eeb1 pa_context_new_with_proplist (libpulse.so.0) #6 0x00007f81c03c72d7 context_connect (libcanberra-pulse.so) #7 0x00007f81c03c77c1 context_state_cb (libcanberra-pulse.so) #8 0x00007f81df77f3df pa_context_set_state (libpulse.so.0) #9 0x00007f81d59e46cd do_pstream_read_write (libpulsecommon-5.0.so) #10 0x00007f81df7944d7 pa_mainloop_dispatch (libpulse.so.0) #11 0x00007f81df7948dc pa_mainloop_iterate (libpulse.so.0) #12 0x00007f81df794980 pa_mainloop_run (libpulse.so.0) #13 0x00007f81df7a2be6 thread (libpulse.so.0) #14 0x00007f81d59f4888 internal_thread_func (libpulsecommon-5.0.so) #15 0x00007f81d5fe352a start_thread (libpthread.so.0) #16 0x00007f81d5d1f77d __clone (libc.so.6) Stack trace of thread 2017: #0 0x00007f81d5fe8590 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f81d2ac561d PR_WaitCondVar (libnspr4.so) #2 0x00007f81de793636 _ZN2js14GCHelperThread10threadLoopEv (libmozjs-24.so) #3 0x00007f81d2acae6b _pt_root (libnspr4.so) #4 0x00007f81d5fe352a start_thread (libpthread.so.0) #5 0x00007f81d5d1f77d __clone (libc.so.6)
Please check the full journal log, there might be more information there. Can you figure out specific steps to reproduce?
(In reply to comment #0) > I was playing on my terminal, gnome session on wayland crashed abruptly and > took me to login screen again. That's no fun. > Jan 07 12:32:53 h3xor systemd-coredump[3676]: Process 1958 (gnome-shell) of > user 1000 dumped core. > > Stack trace of thread 1958: > #0 0x00007f81d7821c60 g_logv (libglib-2.0.so.0) > #1 0x00007f81d7821e9f g_log (libglib-2.0.so.0) > #2 0x00007f81db33ab9e x_io_error (libmutter.so.0) So an X IO error means that the X server (Xwayland) went away. So it seems like the root cause is probably either in Xwayland or mutter.
(In reply to comment #1) > Please check the full journal log, there might be more information there. > > Can you figure out specific steps to reproduce? I checked the journal log, there is nothing specific related to it in the journal log that I could find. And unfortunately, that was abrupt, but the next time it happens, I will keep a track of things.
(In reply to comment #2) > (In reply to comment #0) > > I was playing on my terminal, gnome session on wayland crashed abruptly and > > took me to login screen again. > That's no fun. > > > Jan 07 12:32:53 h3xor systemd-coredump[3676]: Process 1958 (gnome-shell) of > > user 1000 dumped core. > > > > Stack trace of thread 1958: > > #0 0x00007f81d7821c60 g_logv (libglib-2.0.so.0) > > #1 0x00007f81d7821e9f g_log (libglib-2.0.so.0) > > #2 0x00007f81db33ab9e x_io_error (libmutter.so.0) > So an X IO error means that the X server (Xwayland) went away. > > So it seems like the root cause is probably either in Xwayland or mutter. Yeah, that's no fun. I would be happy to give out more information which would help in debugging. But that strace was the only thing I could get out of it. If there is any flag of some sort I can turn on for verbosity, it can help the next time I hit it.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.