Hey,
Debian wayland compositor doesn't always register correct keycodes. This
can be programmatically reproduced every time, but impacts actual users
mostly on systems with higher latency, such as accessing remote virtual
machines over spice:
https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/14
The bug can be reproduced using Timo's instructions even on a local
virtual machine:
https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/14#note_1831985
This will produce incorrect output and log warnings to journal:
Jul 11 12:33:25 testing gnome-shell[3248]: Window manager warning: last_user_time (85093) is greater than comparison timestamp (85091). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Jul 11 12:33:25 testing gnome-shell[3248]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 85093. Working around...
I originally ran into this on Debian 12, but tested that this hasn't
been fixed in the newest experimental release either.
I've only been able to reproduce this on Debian && GNOME && wayland
combination. This can't be reproduced on GNOME && Xorg, virtual
consoles, Weston nor in arch linux && GNOME && wayland combination.
Furthermore, arch wayland build has the same version as the current
experimental libwayland-client0:
$ pacman -Q wayland
wayland 1.22.0-1
leading me to believe the bug is somewhere in the Debian wayland
compositor build.
Cheers,
Juho Kuisma