GNOME Bugzilla – Bug 741494
GNOME Wayland session fails to start if pointer device is not available
Last modified: 2021-07-05 14:35:45 UTC
Hello! This bug originally spotted here: https://bugzilla.gnome.org/show_bug.cgi?id=740518 The crash in the linked bug report happened because clutter identified my mouse as a keyboard, so GNOME Shell (on Wayland) thought I didn't have a mouse. Instead of mouse not working, GNOME on Wayland crashes in that case (backtrace in comment 10 there). GNOME on X doesn't crash in similar situation. Examples for how to reproduce from VT: Run when mouse is unplugged: $ gnome-shell --wayland --display-server If mouse and keyboard share same USB stick: $ sleep 5; gnome-shell --wayland --display-server (5 seconds to unplug stick) Any other way that disables the mouse will work too (like "sudo rm /dev/input/eventX").
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.