GNOME Bugzilla – Bug 795537
Crash when resume from screenlock
Last modified: 2021-07-05 13:53:21 UTC
Created attachment 371367 [details] output of "journalctl -xb" Arch Linux GNOME Shell 3.28.1 on Wayland Sometimes when I press ENTER to turn on the display the gnome session crashes and returns to the GDM login screen. I attach the last part of output of "journalctl -xb". I think the relevant part is this: .... abr 23 15:57:00 arch-juan kernel: traps: gnome-shell[662] general protection ip:7f625cc81191 sp:7fff0e798b68 error:0 in libgobject-2.0.so.0.5600.1[7f625cc4b000+52000] abr 23 15:57:00 arch-juan systemd[1]: Created slice system-systemd\x2dcoredump.slice. -- Subject: Unit system-systemd\x2dcoredump.slice has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit system-systemd\x2dcoredump.slice has finished starting up. -- -- The start-up result is RESULT. abr 23 15:57:00 arch-juan systemd[1]: Started Process Core Dump (PID 15401/UID 0). -- Subject: Unit systemd-coredump@0-15401-0.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump@0-15401-0.service has finished starting up. -- -- The start-up result is RESULT. abr 23 15:57:03 arch-juan gnome-documents[1644]: Error reading events from display: Tubería rota abr 23 15:57:03 arch-juan unknown[6188]: Error reading events from display: Tubería rota abr 23 15:57:03 arch-juan gnome-session[618]: gnome-session-binary[618]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 abr 23 15:57:03 arch-juan polkitd[504]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.21, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale es_ES.UTF-8) (disconnected from bus) abr 23 15:57:03 arch-juan org.gnome.Shell.desktop[662]: (EE) abr 23 15:57:03 arch-juan org.gnome.Shell.desktop[662]: Fatal server error: abr 23 15:57:03 arch-juan org.gnome.Shell.desktop[662]: (EE) failed to read Wayland events: Connection reset by peer abr 23 15:57:03 arch-juan org.gnome.Shell.desktop[662]: (EE) abr 23 15:57:03 arch-juan lollypop[6168]: Error reading events from display: Tubería rota abr 23 15:57:03 arch-juan gnome-session-binary[618]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 abr 23 15:57:03 arch-juan unknown[1221]: Error reading events from display: Tubería rota abr 23 15:57:03 arch-juan systemd[542]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE abr 23 15:57:03 arch-juan systemd[542]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. abr 23 15:57:03 arch-juan gdm-autologin][538]: pam_unix(gdm-autologin:session): session closed for user juan abr 23 15:57:03 arch-juan gnome-session-binary[618]: Unrecoverable failure in required component org.gnome.Shell.desktop abr 23 15:57:03 arch-juan pulseaudio[742]: ICE default IO error handler doing an exit(), pid = 742, errno = 11 abr 23 15:57:03 arch-juan systemd[1]: Started Process Core Dump (PID 15409/UID 0). ....
$ coredumpctl info -1 gnome-shell PID: 15733 (gnome-shell) UID: 1000 (juan) GID: 1000 (juan) Signal: 11 (SEGV) Timestamp: Wed 2018-04-25 12:37:46 CEST (59min ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-1000.slice/session-c3.scope Unit: session-c3.scope Slice: user-1000.slice Session: c3 Owner UID: 1000 (juan) Boot ID: ce6a32d1d8f1443d86d722df36a412ed Machine ID: f10a639e435b4ee984fbe766ef8d884f Hostname: arch-juan Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.ce6a32d1d8f1443d86d722df36a412ed.15733.1524652666000000.lz4 Message: Process 15733 (gnome-shell) of user 1000 dumped core. Stack trace of thread 15733: #0 0x00007fe7ce84c191 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0) #1 0x00007fe7ce82a6ff g_object_ref (libgobject-2.0.so.0) #2 0x00007fe7cc5737b7 st_theme_get_custom_stylesheets (libst-1.0.so) #3 0x00007fe7c901d1c8 ffi_call_unix64 (libffi.so.6) #4 0x00007fe7c901cc2a ffi_call (libffi.so.6) #5 0x00007fe7cd51326b n/a (libgjs.so.0) #6 0x00007fe7cd514c27 n/a (libgjs.so.0) #7 0x00007fe7c60403a1 n/a (libmozjs-52.so.0) #8 0x00007fe7c6045f11 n/a (libmozjs-52.so.0) #9 0x00007fe7c603f4ae n/a (libmozjs-52.so.0) #10 0x00007fe7c6040204 n/a (libmozjs-52.so.0) #11 0x00007fe7c60406b8 n/a (libmozjs-52.so.0) #12 0x00007fe7c5d3f5d3 n/a (libmozjs-52.so.0) #13 0x000018c88c19cab6 n/a (n/a) #14 0x00007fe7c5c6b6bd n/a (libmozjs-52.so.0) #15 0x00007fe7c6052936 n/a (libmozjs-52.so.0) #16 0x00007fe7c603f4ae n/a (libmozjs-52.so.0) #17 0x00007fe7c6040204 n/a (libmozjs-52.so.0) #18 0x00007fe7c60406b8 n/a (libmozjs-52.so.0) #19 0x00007fe7c5dc75c6 _Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE (libmozjs-52.so.0) #20 0x00007fe7cd538ea8 gjs_call_function_value (libgjs.so.0) #21 0x00007fe7cd50d881 gjs_closure_invoke (libgjs.so.0) #22 0x00007fe7cd52c259 n/a (libgjs.so.0) #23 0x00007fe7ce825a4d g_closure_invoke (libgobject-2.0.so.0) #24 0x00007fe7ce84296e n/a (libgobject-2.0.so.0) #25 0x00007fe7ce54b1d6 g_main_context_dispatch (libglib-2.0.so.0) #26 0x00007fe7ce54b5b1 n/a (libglib-2.0.so.0) #27 0x00007fe7ce54b8e2 g_main_loop_run (libglib-2.0.so.0) #28 0x00007fe7cca484b0 meta_run (libmutter-2.so.0) #29 0x000055e00f9faff1 n/a (gnome-shell) #30 0x00007fe7cf270f4a n/a (/usr/lib/libc-2.26.so (deleted)) $ coredumpctl info -1 Xwayland PID: 15753 (Xwayland) UID: 1000 (juan) GID: 1000 (juan) Signal: 6 (ABRT) Timestamp: Wed 2018-04-25 12:37:49 CEST (59min ago) Command Line: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 Executable: /usr/bin/Xwayland Control Group: /user.slice/user-1000.slice/session-c3.scope Unit: session-c3.scope Slice: user-1000.slice Session: c3 Owner UID: 1000 (juan) Boot ID: ce6a32d1d8f1443d86d722df36a412ed Machine ID: f10a639e435b4ee984fbe766ef8d884f Hostname: arch-juan Storage: /var/lib/systemd/coredump/core.Xwayland.1000.ce6a32d1d8f1443d86d722df36a412ed.15753.1524652669000000.lz4 Message: Process 15753 (Xwayland) of user 1000 dumped core. Stack trace of thread 15753: #0 0x00007f196c8a9860 n/a (/usr/lib/libc-2.26.so (deleted)) #1 0x00007fffc9f4fed0 n/a (n/a)
It just happened to me again right now. The coredump output looks different: PID: 698 (Xwayland) UID: 1000 (juan) GID: 1000 (juan) Signal: 6 (ABRT) Timestamp: Wed 2018-04-25 15:09:26 CEST (1min 23s ago) Command Line: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 Executable: /usr/bin/Xwayland Control Group: /user.slice/user-1000.slice/session-c1.scope Unit: session-c1.scope Slice: user-1000.slice Session: c1 Owner UID: 1000 (juan) Boot ID: f06a40a7ba0d4590a973a9e55ef9f46f Machine ID: f10a639e435b4ee984fbe766ef8d884f Hostname: arch-juan Storage: /var/lib/systemd/coredump/core.Xwayland.1000.f06a40a7ba0d4590a973a9e55ef9f46f.698.1524661766000000.lz4 Message: Process 698 (Xwayland) of user 1000 dumped core. Stack trace of thread 698: #0 0x00007f2330ce7efb raise (libc.so.6) #1 0x00007f2330ce92c1 abort (libc.so.6) #2 0x000055a95c5c5cda OsAbort (Xwayland) #3 0x000055a95c5cb7f3 n/a (Xwayland) #4 0x000055a95c5cc615 FatalError (Xwayland) #5 0x000055a95c457bdf n/a (Xwayland) #6 0x000055a95c5c3851 n/a (Xwayland) #7 0x000055a95c5bc6fb WaitForSomething (Xwayland) #8 0x000055a95c588503 n/a (Xwayland) #9 0x000055a95c58c7a0 n/a (Xwayland) #10 0x00007f2330cd49a7 __libc_start_main (libc.so.6) #11 0x000055a95c45723a _start (Xwayland) Stack trace of thread 701: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 702: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 705: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 706: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 708: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 703: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 704: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) Stack trace of thread 707: #0 0x00007f233107b07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f2329fbd0f4 n/a (swrast_dri.so) #2 0x00007f2329fbcf48 n/a (swrast_dri.so) #3 0x00007f23310750bc start_thread (libpthread.so.0) #4 0x00007f2330daa2ff __clone (libc.so.6) PID: 650 (gnome-shell) UID: 1000 (juan) GID: 1000 (juan) Signal: 11 (SEGV) Timestamp: Wed 2018-04-25 15:09:24 CEST (1min 29s ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-1000.slice/session-c1.scope Unit: session-c1.scope Slice: user-1000.slice Session: c1 Owner UID: 1000 (juan) Boot ID: f06a40a7ba0d4590a973a9e55ef9f46f Machine ID: f10a639e435b4ee984fbe766ef8d884f Hostname: arch-juan Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.f06a40a7ba0d4590a973a9e55ef9f46f.650.1524661764000000.lz4 Message: Process 650 (gnome-shell) of user 1000 dumped core. Stack trace of thread 650: #0 0x00007febffddf191 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0) #1 0x00007febffdbd6ff g_object_ref (libgobject-2.0.so.0) #2 0x00007febfdb067b7 st_theme_get_custom_stylesheets (libst-1.0.so) #3 0x00007febfa5b01c8 ffi_call_unix64 (libffi.so.6) #4 0x00007febfa5afc2a ffi_call (libffi.so.6) #5 0x00007febfeaa626b n/a (libgjs.so.0) #6 0x00007febfeaa7c27 n/a (libgjs.so.0) #7 0x00007febf758b3a1 n/a (libmozjs-52.so.0) #8 0x00007febf7590f11 n/a (libmozjs-52.so.0) #9 0x00007febf758a4ae n/a (libmozjs-52.so.0) #10 0x00007febf758b204 n/a (libmozjs-52.so.0) #11 0x00007febf758b6b8 n/a (libmozjs-52.so.0) #12 0x00007febf728a5d3 n/a (libmozjs-52.so.0) #13 0x00002e77acdfcab6 n/a (n/a) #14 0x00007febf71b66bd n/a (libmozjs-52.so.0) #15 0x00007febf759d936 n/a (libmozjs-52.so.0) #16 0x00007febf758a4ae n/a (libmozjs-52.so.0) #17 0x00007febf758b204 n/a (libmozjs-52.so.0) #18 0x00007febf758b6b8 n/a (libmozjs-52.so.0) #19 0x00007febf73125c6 _Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE (libmozjs-52.so.0) #20 0x00007febfeacbea8 gjs_call_function_value (libgjs.so.0) #21 0x00007febfeaa0881 gjs_closure_invoke (libgjs.so.0) #22 0x00007febfeabf259 n/a (libgjs.so.0) #23 0x00007febffdb8a4d g_closure_invoke (libgobject-2.0.so.0) #24 0x00007febffdd596e n/a (libgobject-2.0.so.0) #25 0x00007febffade1d6 g_main_context_dispatch (libglib-2.0.so.0) #26 0x00007febffade5b1 n/a (libglib-2.0.so.0) #27 0x00007febffade8e2 g_main_loop_run (libglib-2.0.so.0) #28 0x00007febfdfdb4b0 meta_run (libmutter-2.so.0) #29 0x0000558eb1217ff1 n/a (gnome-shell) #30 0x00007fec008049a7 __libc_start_main (libc.so.6) #31 0x0000558eb121814a n/a (gnome-shell) Stack trace of thread 720: #0 0x00007fec008cfcd9 __poll (libc.so.6) #1 0x00007febe0784773 n/a (libpulse.so.0) #2 0x00007febe0775bd0 pa_mainloop_poll (libpulse.so.0) #3 0x00007febe0776271 pa_mainloop_iterate (libpulse.so.0) #4 0x00007febe0776301 pa_mainloop_run (libpulse.so.0) #5 0x00007febe07846ae n/a (libpulse.so.0) #6 0x00007febe052381c n/a (libpulsecommon-11.1.so) #7 0x00007fec00ba50bc start_thread (libpthread.so.0) #8 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 795: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 652: #0 0x00007fec008cfcd9 __poll (libc.so.6) #1 0x00007febffade523 n/a (libglib-2.0.so.0) #2 0x00007febffade63e g_main_context_iteration (libglib-2.0.so.0) #3 0x00007febffade692 n/a (libglib-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 790: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 800: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 797: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 798: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 796: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 801: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 794: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 799: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 8260: #0 0x00007fec008d4f09 syscall (libc.so.6) #1 0x00007febffb2552d g_cond_wait_until (libglib-2.0.so.0) #2 0x00007febffab0903 n/a (libglib-2.0.so.0) #3 0x00007febffb07436 n/a (libglib-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 8249: #0 0x00007fec008d4f09 syscall (libc.so.6) #1 0x00007febffb2552d g_cond_wait_until (libglib-2.0.so.0) #2 0x00007febffab0903 n/a (libglib-2.0.so.0) #3 0x00007febffb07436 n/a (libglib-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 677: #0 0x00007fec008cfcd9 __poll (libc.so.6) #1 0x00007febffade523 n/a (libglib-2.0.so.0) #2 0x00007febffade63e g_main_context_iteration (libglib-2.0.so.0) #3 0x00007febe8576f4e n/a (libdconfsettings.so) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 792: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 791: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 793: #0 0x00007fec00bab07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007febf70fdd2d n/a (libmozjs-52.so.0) #2 0x00007febf759e72a n/a (libmozjs-52.so.0) #3 0x00007febf75677ca n/a (libmozjs-52.so.0) #4 0x00007fec00ba50bc start_thread (libpthread.so.0) #5 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 653: #0 0x00007fec008cfcd9 __poll (libc.so.6) #1 0x00007febffade523 n/a (libglib-2.0.so.0) #2 0x00007febffade8e2 g_main_loop_run (libglib-2.0.so.0) #3 0x00007fec000cd348 n/a (libgio-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 8258: #0 0x00007fec008d4f09 syscall (libc.so.6) #1 0x00007febffb2552d g_cond_wait_until (libglib-2.0.so.0) #2 0x00007febffab0903 n/a (libglib-2.0.so.0) #3 0x00007febffb07436 n/a (libglib-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 8259: #0 0x00007fec008d4f09 syscall (libc.so.6) #1 0x00007febffb2552d g_cond_wait_until (libglib-2.0.so.0) #2 0x00007febffab0903 n/a (libglib-2.0.so.0) #3 0x00007febffb07436 n/a (libglib-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6) Stack trace of thread 8261: #0 0x00007fec008d4f09 syscall (libc.so.6) #1 0x00007febffb2552d g_cond_wait_until (libglib-2.0.so.0) #2 0x00007febffab0903 n/a (libglib-2.0.so.0) #3 0x00007febffb07436 n/a (libglib-2.0.so.0) #4 0x00007febffb06a2a n/a (libglib-2.0.so.0) #5 0x00007fec00ba50bc start_thread (libpthread.so.0) #6 0x00007fec008da2ff __clone (libc.so.6)
I have been experiencing this kind of issues for several months now. Below is a recent stack trace of a crashed Xwayland v1.19.6 process. I think its crash was caused by an immediately preceding gnome-shell crash, because the crash is simply a SIGABRT on some assertion accompanied by "failed to read Wayland events" message. The error happens around here (adjusted to the current xorg source): https://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayland/xwayland.c#n810 I do not have a backtrace for the crashed gnome-shell yet, but I will try to post it here when it happens again. Xwayland backtrace:
+ Trace 238660
There was another crash, so I have new core dumps for both Xwayland and gnome-shell. I use Intel GPU and the display is configured with "Scale" of 200%. gnome-shell backtrace:
+ Trace 238663
The crashes happen regularly, so this should be given a high priority. It may have something to do with HiDPI configuration, because I have another computer with similar hardware (also Intel graphics, but older) and almost the same OS and other software, but without a HiDPI configuration and I do not experience similar issues there. Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. backtrace:
+ Trace 238664
Hey, Do you have an easy reproducer for this? As I also notice many automatic error reports related to this, but I struggle a bit in understanding some aspects, as memory-wise I don't see anything clearly wrong. If you can help me in debugging, ping me as Trevinho in gimpnet/freenode. Cheers
Hi, I do not have a reliable way to reproduce this bug, I am sorry. I only have a way which "works for me" around 40%-50% of the time: 1. In Gnome Settings->Power set "Blank screen" setting to the lowest possible value (1 minute). I also leave the Privacy->Screen Lock option disabled, but maybe it can also be enabled and the result would be the same. I am not sure, because I did not try that. 2. Wait until the screen gets blank. Then move the mouse or press some keyboard button. At around 40% to 50% of cases, the entire gnome-shell process crashes and the GDM login screen appears instead of the previously running session. All the Gnome Shell extensions are disabled and no non-standard applications are running in my session. I was able to reproduce crash with only one desktop application running, namely Firefox Nightly. It may be possible that Firefox actually causes Gnome Shell to crash, but I am not sure and I do not know how to check this. In the meantime, there was a slight change in behavior, probably caused by some recent Gnome Shell or Xwayland update. The Xwayland process no longer crashes together with Gnome Shell. But Gnome Shell still crashes as before. The backtrace seems to be very similar: Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 238672
Has this bug ever been reported on mesa? The crash is inside mesa, which should never happen.
(In reply to Jonas Ådahl from comment #8) > Has this bug ever been reported on mesa? The crash is inside mesa, which > should never happen. No, to the best of my knowledge, it has not. Thanks for mentioning mesa, I have just created one on freedesktop Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107520
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/mutter/-/issues/ Thank you for your understanding and your help.