GNOME Bugzilla – Bug 775337
Shouldn't try to run the fail whale if gnome-shell crashed on Wayland
Last modified: 2021-06-14 18:21:24 UTC
While running GNOME inside a qemu/kvm VM (installed using virt-manager), I could observe GNOME not coming up and leaving a black screen. The underlying issue could be found (well, sort of.. seems libinput is causing some trouble there) But, at the same time, I observed gnome-session-failed crashing in gtk, and thus not being able to show the 'fail whale' picture (not, that this would have made things work, but it would have been more obvious than a black screen) a backtrace of gnome-session-failed looked like this: (gdb) bt
+ Trace 236901
(adjusting version - this was actually tested / seen with gtk 3.22.4)
*** Bug 775463 has been marked as a duplicate of this bug. ***
(In reply to Dominique Leuenberger from comment #0) > While running GNOME inside a qemu/kvm VM (installed using virt-manager), I > could observe GNOME not coming up and leaving a black screen. > > The underlying issue could be found (well, sort of.. seems libinput is > causing some trouble there) > > But, at the same time, I observed gnome-session-failed crashing in gtk, and > thus not being able to show the 'fail whale' picture (not, that this would > have made things work, but it would have been more obvious than a black > screen) I'm guessing that, in your logs, you'll see gnome-shell crashing before the gnome-session helper here, and that you're using Wayland, correct?
(In reply to Bastien Nocera from comment #3) > I'm guessing that, in your logs, you'll see gnome-shell crashing before the > gnome-session helper here, and that you're using Wayland, correct? gnome-shell did report to have 'failed' before - but there were no usabe crash logs. The best I could find was some X issues with XInputExtension like: Nov 21 08:58:21 germ202 org.gnome.Shell.desktop[1828]: X Error of failed request: BadValue (integer parameter out of range for operation) Nov 21 08:58:21 germ202 org.gnome.Shell.desktop[1828]: Major opcode of failed request: 131 (XInputExtension) Nov 21 08:58:21 germ202 org.gnome.Shell.desktop[1828]: Minor opcode of failed request: 57 () Nov 21 08:58:21 germ202 org.gnome.Shell.desktop[1828]: Value in failed request: 0x108 Nov 21 08:58:21 germ202 org.gnome.Shell.desktop[1828]: Serial number of failed request: 274 Nov 21 08:58:21 germ202 org.gnome.Shell.desktop[1828]: Current serial number in output stream: 275 This then lead me to remove xf86-libinput to get the system 'running'
Likely 5c46094d67f2e5cdafe6edcfd8c0d5894a2dafc6 in mutter (for bug 771744). If you could verify, I can repurpose the bug for the gnome-session-failed crash.
(In reply to Bastien Nocera from comment #5) > Likely 5c46094d67f2e5cdafe6edcfd8c0d5894a2dafc6 in mutter (for bug 771744). > > If you could verify, I can repurpose the bug for the gnome-session-failed > crash. Happy to confirm that this fix indeed fixes the underlying issue of mutter / gnome-shell disappearing and thus eliminating the need for gnome-session-failed trying to show (libinput driver installed again)
(In reply to Bastien Nocera from comment #5) > Likely 5c46094d67f2e5cdafe6edcfd8c0d5894a2dafc6 in mutter (for bug 771744). > > If you could verify, I can repurpose the bug for the gnome-session-failed > crash. Moving to gnome-session, then
On Wayland, gnome-shell/mutter is the Wayland compositor so if/when it crashes it's unlikely anything at all will be able to show up on the screen (unlike X11 where the X server is still running even after gnome-shell/mutter has vanished)
*** Bug 772368 has been marked as a duplicate of this bug. ***
*** Bug 776096 has been marked as a duplicate of this bug. ***
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 of gnome-session, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-session/-/issues/ Thank you for your understanding and your help.