GNOME Bugzilla – Bug 768774
Crashed after entering Kerberos password via a system modal dialog
Last modified: 2021-07-05 14:28:29 UTC
To test some memory leaks in gnome-online-accounts, I created a new Kerberos account via Settings -> Online Accounts. gnome-shell crashed as soon as I finished entering the password via the system modal dialog. gnome-shell-3.18.5-1.fc23.x86_64 mutter-3.18.4-1.fc23.x86_64 xorg-x11-server-Xorg-1.18.3-2.fc23.x86_64 Stack trace of thread 1872: #0 0x00007fedde818a28 __GI_raise (libc.so.6) #1 0x00007fedde81a62a __GI_abort (libc.so.6) #2 0x00007fede0409a95 g_assertion_message (libglib-2.0.so.0) #3 0x00007fede0409b2a g_assertion_message_expr (libglib-2.0.so.0) #4 0x00007fede3fb56ca meta_window_unmanage (libmutter.so.0) #5 0x00007fede3fc11a6 handle_other_xevent (libmutter.so.0) #6 0x00007fede3fc1d4b xevent_filter (libmutter.so.0) #7 0x00007fede152de01 gdk_event_apply_filters (libgdk-3.so.0) #8 0x00007fede152e0c0 _gdk_x11_display_queue_events (libgdk-3.so.0) #9 0x00007fede15002c9 gdk_display_get_event (libgdk-3.so.0) #10 0x00007fede152de82 gdk_event_source_dispatch (libgdk-3.so.0) #11 0x00007fede03e3e5a g_main_dispatch (libglib-2.0.so.0) #12 0x00007fede03e41f0 g_main_context_iterate (libglib-2.0.so.0) #13 0x00007fede03e4512 g_main_loop_run (libglib-2.0.so.0) #14 0x00007fede3fa307c meta_run (libmutter.so.0) #15 0x000055d05e9cc7c7 main (gnome-shell) #16 0x00007fedde804580 __libc_start_main (libc.so.6) #17 0x000055d05e9cc909 _start (gnome-shell) Stack trace of thread 1905: #0 0x00007fedde8dab1d poll (libc.so.6) #1 0x00007fede03e418c g_main_context_poll (libglib-2.0.so.0) #2 0x00007fede03e4512 g_main_loop_run (libglib-2.0.so.0) #3 0x00007fede1883516 gdbus_shared_thread_func (libgio-2.0.so.0) #4 0x00007fede040a8e5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007feddebac61a start_thread (libpthread.so.0) #6 0x00007fedde8e659d __clone (libc.so.6) Stack trace of thread 1899: #0 0x00007fedde8dab1d poll (libc.so.6) #1 0x00007fede03e418c g_main_context_poll (libglib-2.0.so.0) #2 0x00007fede03e429c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fede03e42d9 glib_worker_main (libglib-2.0.so.0) #4 0x00007fede040a8e5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007feddebac61a start_thread (libpthread.so.0) #6 0x00007fedde8e659d __clone (libc.so.6) Stack trace of thread 1907: #0 0x00007fedde8dab1d poll (libc.so.6) #1 0x00007fede03e418c g_main_context_poll (libglib-2.0.so.0) #2 0x00007fede03e429c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fedc76182ad dconf_gdbus_worker_thread (libdconfsettings.so) #4 0x00007fede040a8e5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007feddebac61a start_thread (libpthread.so.0) #6 0x00007fedde8e659d __clone (libc.so.6) Stack trace of thread 1910: #0 0x00007feddebb1b20 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007feddb40ad30 PR_WaitCondVar (libnspr4.so) #2 0x00007fede72a3046 _ZN2js22SourceCompressorThread16compressorThreadEPv (libmozjs-24.so) #3 0x00007feddb41065b _pt_root (libnspr4.so) #4 0x00007feddebac61a start_thread (libpthread.so.0) #5 0x00007fedde8e659d __clone (libc.so.6) Stack trace of thread 4706: #0 0x00007fedde8e07a9 syscall (libc.so.6) #1 0x00007fede04289fa g_cond_wait_until (libglib-2.0.so.0) #2 0x00007fede03b8c19 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0) #3 0x00007fede03b923b g_async_queue_timeout_pop (libglib-2.0.so.0) #4 0x00007fede040b33a g_thread_pool_wait_for_new_pool (libglib-2.0.so.0) #5 0x00007fede040a8e5 g_thread_proxy (libglib-2.0.so.0) #6 0x00007feddebac61a start_thread (libpthread.so.0) #7 0x00007fedde8e659d __clone (libc.so.6) Stack trace of thread 1908: #0 0x00007fedde8dab1d poll (libc.so.6) #1 0x00007fede82198a1 poll_func (libpulse.so.0) #2 0x00007fede820aec1 pa_mainloop_poll (libpulse.so.0) #3 0x00007fede820b55e pa_mainloop_iterate (libpulse.so.0) #4 0x00007fede820b610 pa_mainloop_run (libpulse.so.0) #5 0x00007fede8219836 thread (libpulse.so.0) #6 0x00007fedde5b7c78 internal_thread_func (libpulsecommon-7.1.so) #7 0x00007feddebac61a start_thread (libpthread.so.0) #8 0x00007fedde8e659d __clone (libc.so.6) Stack trace of thread 1909: #0 0x00007feddebb1b20 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007feddb40ad30 PR_WaitCondVar (libnspr4.so) #2 0x00007fede722f69e _ZN2js14GCHelperThread10threadLoopEv (libmozjs-24.so) #3 0x00007feddb41065b _pt_root (libnspr4.so) #4 0x00007feddebac61a start_thread (libpthread.so.0) #5 0x00007fedde8e659d __clone (libc.so.6)
gnome-shell crashed in debian unstable. I was just starting a VM in Virtualbox. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGABRT, Aborted.
+ Trace 236577
Relevant journalctl logs: Aug 24 18:21:22 unstable org.gnome.Shell.desktop[3644]: Gjs-Message: JS LOG: Failed to read extents of focused component: timeout from dbind Aug 24 18:21:29 unstable org.gnome.Shell.desktop[3644]: ** Aug 24 18:21:29 unstable org.gnome.Shell.desktop[3644]: mutter:ERROR:core/window.c:1360:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Aug 24 18:21:30 unstable polkitd(authority=local)[2547]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.42, object path /org/freedesktop/PolicyKit1/ Aug 24 18:21:39 unstable gnome-session[3551]: gnome-session-binary[3551]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Aug 24 18:21:39 unstable gnome-session-binary[3551]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Aug 24 18:21:44 unstable org.gnome.Shell.desktop[30190]: Gjs-Message: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or dir Aug 24 18:21:45 unstable org.gnome.Shell.desktop[30190]: Gjs-Message: JS WARNING: [/home/dev/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com/exten Aug 24 18:21:45 unstable org.gnome.Shell.desktop[30190]: Gjs-Message: JS LOG: System monitor applet init from /home/dev/.local/share/gnome-shell/extensions/system-monitor@par Aug 24 18:21:45 unstable org.gnome.Shell.desktop[30190]: Gjs-Message: JS LOG: System monitor applet enabling Aug 24 18:21:45 unstable org.gnome.Shell.desktop[30190]: Gjs-Message: JS LOG: System monitor applet enabling done
Please change the bug summary into something less specific.
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.