I bisected mutter and gnome-shell until I identified the revision in mutter that caused the regression: https://gitlab.gnome.org/GNOME/mutter/-/commit/26676a829e74859488154cd8c45de1d0b629f3ca.
More specifically, the changes to src/core/events.c. Indeed I rebuilt mutter in jammy with the following patch, and the issue with the firefox snap was gone:
--- a/src/core/events.c +++ b/src/core/events.c @@ -523,10 +523,6 @@ meta_display_handle_event (MetaDisplay #ifdef HAVE_WAYLAND if (wayland_compositor && !bypass_wayland) { - if (window && event->type == CLUTTER_MOTION && - event->any.time != CLUTTER_CURRENT_TIME) - meta_window_check_alive_on_event (window, event->any.time); - if (meta_wayland_compositor_handle_event (wayland_compositor, event)) bypass_clutter = TRUE; }
I bisected mutter and gnome-shell until I identified the revision in mutter that caused the regression: https:/ /gitlab. gnome.org/ GNOME/mutter/ -/commit/ 26676a829e74859 488154cd8c45de1 d0b629f3ca.
More specifically, the changes to src/core/events.c. Indeed I rebuilt mutter in jammy with the following patch, and the issue with the firefox snap was gone:
--- a/src/core/events.c handle_ event (MetaDisplay CURRENT_ TIME) check_alive_ on_event (window, event->any.time); compositor_ handle_ event (wayland_ compositor, event))
bypass_ clutter = TRUE;
+++ b/src/core/events.c
@@ -523,10 +523,6 @@ meta_display_
#ifdef HAVE_WAYLAND
if (wayland_compositor && !bypass_wayland)
{
- if (window && event->type == CLUTTER_MOTION &&
- event->any.time != CLUTTER_
- meta_window_
-
if (meta_wayland_
}