https://bugzilla.gnome.org/show_bug.cgi?id=777693
--- Comment #10 from Olivier Fourdan <ofour...@redhat.com> ---
Yes, possibly.
> Key repeat discarded, Wayland compositor doesn't seem to be processing events
> fast enough!
This message comes from Xwayland's patch to address this issue precisely:
https://cgit.freedesktop.org/xorg/xserver/commit/?id=239705a
In Wayland, the clients implement key repeats (unlikle X11 where the Xserver
implements key repeats), but the actual key press/release come from the Wayland
compositor that needs to process these first and notify the clients.
What happens in this case is the Wayland compositor mutter/gnome-shell is busy
playing an animation and doesn't process the key events fast enough, and the
client (Xwayland) is not notified the key was released, and starts repeating
the last known key press.
To avoid this behavior, Xwayland will "ping" the Wayland compositor prior to
repeating the key press, and if it doesn't get a reply from the compositor will
assume it's too busy and will print this message instead of issuing the key
repeat.
The fact that this occurs when playing an animation was discusses here:
https://bugzilla.gnome.org/show_bug.cgi?id=762618#c11
But the message from Xwayland shows that the mechanism is working (in Xwayland)
and prevents the key repeat from occurring when the compositor is not
processing events.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
