GNOME Bugzilla – Bug 787969
seg fault in libmutter.so when boot with autologin and no connecting to monitors
Last modified: 2021-07-05 14:10:57 UTC
This happened on ubuntu 17.10(artful),I think this is a universe bug with gnome-shell. reproduce steps: 1. set autologin 2.boot system with no monitors connect 3.connect to a monitor Then, you will find autologin didn't work ,and segfault in syslog like this : ep 20 15:56:49 liuyi-Vostro-3900 kernel: [ 6.173314] gnome-shell[1305]: segfault at 28 ip 00007fe2364c5d74 sp 00007fff31482270 error 4 in libmutter-0.so.0.0.0[7fe23647e000+131000] Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session[1149]: gnome-session-binary[1149]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session-binary[1149]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 20 15:56:50 liuyi-Vostro-3900 kernel: [ 6.459419] gnome-shell[1339]: segfault at 28 ip 00007f98e9d15d74 sp 00007ffe1acf9950 error 4 in libmutter-0.so.0.0.0[7f98e9cce000+131000] Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session[1149]: gnome-session-binary[1149]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session[1149]: gnome-session-binary[1149]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session-binary[1149]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session-binary[1149]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session[1149]: gnome-session-binary[1149]: CRITICAL: We failed, but the fail whale is dead. Sorry.... Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session-binary[1149]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Sep 20 15:56:50 liuyi-Vostro-3900 gnome-session-binary[1149]: CRITICAL: We failed, but the fail whale is dead. Sorry.... I wonder how mutter handle the situation with no monitors.
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and how to make sure to include debug symbols. Thanks in advance!
(In reply to liuyi from comment #0) > I wonder how mutter handle the situation with no monitors. This wasn't supported until very recently (3.25.92 to be exact, released about a fortnight ago), see bug 730551.
i have the same issue, when trying to login to gnome-shell Wayland, uding GDM on Arch. My Log: Sep 21 12:20:21 yuri-Thinkpad-T440 kernel: gnome-shell[1014]: segfault at 8 ip 00007f50a3983a00 sp 00007ffdb95ba3b8 error 4 in libmutter-1.so.0.0.0[7f50a3922000+160000] Sep 21 12:20:22 yuri-Thinkpad-T440 systemd-coredump[1035]: Process 1014 (gnome-shell) of user 1000 dumped core.
(In reply to André Klapper from comment #1) > Thanks for taking the time to report this. > Without a stack trace from the crash it's very hard to determine what caused > it. > Can you get us a stack trace? Please see > https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for > more information on how to do so and how to make sure to include debug > symbols. > Thanks in advance! I got stucked when use gdb via remote ssh connect to the system,this worked on 16.10, but on 17.10,it truned out to be not avaliable although I set env DISPLAY=:0. maybe the use of wayland? I am not sure... Is there any way to get core dump file? Thanks very much！
Created attachment 365308 [details] stack trace I also get this whether auto login is enabled or disabled. Attached a stack trace that I hope is relevant.
Hm, I forgot about debugging symbols, but after building mutter and gnome-shell from git without stripping symbols, I can't seem to be able to reproduces the bug. Maybe it's fixed in a recent commit?
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.