** Description changed: Summary: On Wayland, when auto-repeating one key and then pressing a second key before releasing the first, the second key repeats correctly, but releasing the first key cancels the repeat of the second key even though it is still held down. This breaks cursor navigation and any GTK app (e.g. ptyxis, GNOME Text Editor): holding Up arrow, then pressing Down arrow while still holding Up key should reverse direction continuously, but movement stops when Up key is released. Affected versions: Mutter 50.1 (and 50.x) Reproduced on Ubuntu 26.04 (mutter 50.1-0ubuntu2.2), GNOME Shell 50.1, Wayland Does not reproduce on Mutter 49.1 (same hardware/keyboard) Steps to reproduce: Open ptyxis (or GNOME Text Editor) on a Wayland session. Hold the Up arrow key until it auto-repeats (cursor moves up continuously). While still holding Up, press and hold Down. Expected: Down repeats (cursor moves down continuously). Actual: Down repeats correctly. While still holding Down, release Up. Expected: Down continues repeating (cursor keeps moving down). Actual: Down stops repeating immediately, despite being held. Holding a single key (e.g. backspace, a letter) repeats normally; only the multi-key handoff is broken. Upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/work_items/4980 + + Fixed in main (Gnome 51) + https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4974/diffs + + Requesting an SRU backport to 50.1 in resolute-updates once it lands on + the gnome-50 branch. + + Workaround: GDK_BACKEND=x11 ptyxis.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2163572 Title: wayland: releasing a non-repeating key cancels autorepeat of a held key (regression in 50) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2163572/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
