https://bugs.kde.org/show_bug.cgi?id=474606
--- Comment #17 from Stefan Burnicki <stefan.burni...@burnicki.net> --- I have the same problem. Thanks to the last comments I could also confirm that I don't have the problem with a new user, only the existing one that migrated $HOME for like 2 years. I used ibus once (can't recall why, maybe when trying stuff with fingerprint?), but it's disabled now. I tried to use wayland with and without it, same result: works for new user, does not work for existing user. "journalctl --user-unit plasma-kwin_wayland --boot 0" also contains the following suspicious lines: kwin_wayland_wrapper[135634]: (WW) Option "-listen" for file descriptors is deprecated kwin_wayland_wrapper[135634]: Please use "-listenfd" instead. kwin_wayland_wrapper[135634]: (WW) Option "-listen" for file descriptors is deprecated kwin_wayland_wrapper[135634]: Please use "-listenfd" instead. kwin_wayland_wrapper[135670]: The XKEYBOARD keymap compiler (xkbcomp) reports: kwin_wayland_wrapper[135670]: > Warning: Unsupported maximum keycode 708, clipping. kwin_wayland_wrapper[135670]: > X11 cannot support keycodes above 255. kwin_wayland_wrapper[135670]: Errors from xkbcomp are not fatal to the X server kwin_wayland[135583]: QtDBus: cannot relay signals from parent QObject(0x564c8ae63d50 "") unless they are emitted in the object's thread QThread(0x564c8ab> but so it does for the new user where the input works properly. Running "sudo libinput debug-events" and pressing some keys: event8 KEYBOARD_KEY +1.307s *** (-1) pressed s event8 KEYBOARD_KEY +1.339s *** (-1) pressed d event8 KEYBOARD_KEY +1.387s *** (-1) released event8 KEYBOARD_KEY +1.475s *** (-1) released event8 KEYBOARD_KEY +2.195s KEY_LEFTMETA (125) pressed event8 KEYBOARD_KEY +2.331s KEY_LEFTMETA (125) released Interestingly most keys show as ***(-1), but left meta does not. However, shortcuts like "Alt+Tab" and "Alt+F2" still work, even if the output shows *** (-1) for those keys. With the other user and in X11 session, the output is the same. What also seems weird to me: It's not like the keyboard input is the only thing not working properly: When I open e.g. systemsettings, I can focus an input field and see the blinking cursor. But as soon as I press a key, both the input field and the window seem to lose focus. And even if I click back into the input field, I see a blue focus on the input, but I don't see a blinking cursor and the window still seems to not be focused (telling from the window decoration color). Any ideas if this could hint to a different problem? Otherwise I would try to copy parts of my home folder to the new user and see when it stops working to narrow down the problem. -- You are receiving this mail because: You are watching all bug changes.
