You are not logged in.
Today I did a full upgrade and rebooted to discover this new bug.
Capslock has become intermittent as if it is stuck in a race condition. Holding a key to repeat has also become intermittent.
This issue does not affect TTY.
`libinput debug-events` shows that all key presses are registering, both up and down.
I have no special keyboard config and never switch layout from standard UK 105-key.
> journalctl --user -b -u plasma-kwin_wayland
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: > Warning: Unsupported maximum keycode 708, clipping.
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: > X11 cannot support keycodes above 255.
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: > Warning: Virtual modifier Hyper multiply defined
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: > Using 0, ignoring 0
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: > Warning: Virtual modifier ScrollLock multiply defined
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: > Using 0, ignoring 0
Dec 23 12:36:27 3900x kwin_wayland_wrapper[1609]: Errors from xkbcomp are not fatal to the X server
Edit: -
I just tested typing in SDDM and that is working as normal.
Last edited by Anarchic (2025-12-26 13:48:04)
Offline
I worked out the problem. Unbeknownst to me, a virtual keyboard was activated without being visible on screen. The tray icon for the virtual keyboard was also hidden. The invisible virtual keyboard was interfering with normal keyboard usage.
Troubleshooting
KWin by default only shows the keyboard when a text field is interacted with by touch. Set `KWIN_IM_SHOW_ALWAYS=1` when starting KWin (or the login session) in order to force the keyboard to always pop up.
Offline