gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate()

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6582f375d7b1e6bec0fdee2e9d2ec574844a8457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Also https://errors.ubuntu.com/problem/f3d88d48bae2b5c8c883c91ee37f390d0887819d

[Ernst Persson (ernstp)]

Cherry pick fixes to 22.04?

[Ernst Persson (ernstp)]

Seems like there was a follow up problem? https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2655

[Daniel van Vugt (vanvugt)]

Not necessarily. That may be unrelated (possibly mentions the wrong bug?) because it fixes a problem that's 2 years old.

[Daniel van Vugt (vanvugt)]

If the second fix https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2655 is required then we should say "fixed in 43.1".

[Ari Pollak (aripollak)]

I'd been running into this issue on Ubuntu 22.04 with Google Chrome, GNOME Shell under Wayland, and multiple monitors - opening Chrome will frequently crash my whole GNOME session. I could also reliably reproduce it once Chrome is running by moving a Chrome window to another monitor from the GNOME activities overview. After I built & installed libmutter 42.6 (42.5 was previously installed), the problem went away.

[Daniel van Vugt (vanvugt)]

Also tracking in https://errors.ubuntu.com/problem/f3d88d48bae2b5c8c883c91ee37f390d0887819d

[Daniel van Vugt (vanvugt)]

mutter (43.2-4ubuntu1) lunar; urgency=medium