Follow-up with a narrower lead: the 2.5 source diff names the candidate patches.
Comparing the debian.tar.xz of 50.1-0ubuntu2.4 and 50.1-0ubuntu2.5, seven patches were added. Two of them are the tablet-tool implicit-grab rework from upstream MR 5043 (upstream bug 4303, Ubuntu bug 2169504): ubuntu/wayland-Keep-accounting-for-the-implicitly-grabbed-surfac.patch ubuntu/wayland-Only-use-implicitly-grabbed-surface-of-tools-whil.patch Both are by Carlos Garnacho. Together they introduce meta_wayland_tablet_seat_get_current_surface() and separate "the surface currently under the tablet tool" from "the implicitly grabbed surface", touching src/wayland/meta-wayland-tablet-seat.c, meta-wayland-tablet-tool.c and meta-wayland-seat.c. That is the surface accounting that determines which client holds tablet focus when a pad registers, i.e. the state GTK reads as seat->keyboard_focus when mutter broadcasts wp_tablet_pad_group.mode_switch. The other five added patches are a test-runner helper, two mouse-focus stickiness patches from MR 5036, a Wayland window state-position fix, and a Clutter PROXIMITY_OUT reset. None of those touch the pad path. This makes a kernel A/B test unnecessary for triage: mutter 2.5 has a concrete candidate, and reverting just those two tablet patches would be a much smaller experiment than swapping kernels - though since the kernel and mutter landed in the same upload, the kernel is not formally excluded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172827 Title: gtk4 4.22.4: SIGSEGV in gdk_surface_handle_event() on a tablet-pad event carrying no surface (GDK_PAD_GROUP_MODE) after USB re- enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2172827/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
