I have started to use KDE neon recently and I just love the ways you can add custom keyboard shortcuts to the operating system by default. Unfortunately, I have been experiencing issues with the keyboard since the beginning. I often use these keybindings to navigate and select text in any application: Home/End, Shift+Home/End, Ctrl+Home/End, Ctrl+Shift+Home/End etc. I often find that the key presses do not get registered and I need to press them 2-3 times. This is really frustrating. Has anyone else experienced this? Any ideas where to even start troubleshooting?

I have the same problem with KDE Plasma 5.20.4, linux Mageia 8. (And it does not happen with older version (maybe 5.15) in Mageia 7). I'm glad that I'm not alone.

At first I thought that it's a problem with my Bluetooth keyboard, but even if I plugged it thought USB, the problem still occurs.

It's frustrated that it's random, so I don't know exactly how to reproduce the bug. But I suspect that it has something to do with Xorg or KWin related problem. When it occurs, Xorg is the most active process, though it only use up to about 8-15% CPU resources. My keyboard is lagged but mouse works normally.

And, not only keys is slowed down, also the key combinations is not consistent. Such as, if my active windows i TimeSlotTracker, which has 'F2' is for edit task, if I press Alt+F2 to open Krunner, it takes awhile and open both Krunner and TimeSlotTracker edit window.

P/S: while messing with TimeSlotTracker I think I could reproduce this problem, I'll report this bug soon.

Bug reported: https://bugs.kde.org/show_bug.cgi?id=440097

Hi!

Same here on current neon user edition with 5.22.3. I did think it is that slow as my hardware is a bit older (x220 and a 2012 desktop), so I have to wait until the processes are started, e.g. krunner. Pressing Alt+Space and waiting for about a second I can type the search. If I type directly, the first 2-3 letters are send to the current running application.

I do not know how to debug this as the keyboard buffer itself is working correctly. Must be something about activating the handler outside the current app.

I've tested with OpenSuse Live Tumbleweed 20210802, and it seems that there is NO problem with this version. Anyone can confirm?

KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0

I've installed Suse Leap 15.3 and then installs KDE Plasma 5.22.4, (Frameworks v5.84.0).
Unfortunately that there's still problem. But I figured out that it may relate to configurations (which worked without problem before with previous versions of KDE (5.15 - 5.12)). Freshly created user does not have problem.

Now I tried to reset KDE configs and it's pain to figure which files are KDE configs.

P/S:
Before resetting KDE configs, I clean the ~/.config folder (in text mode), remove all backups and old applications' configs. I avoid to touch any k* files or anything relates to plasma, only kde config files I removed are kglobalshortcutsrc.XXXXXX.

To make sure everything is OK before the resetting, I login to KDE. Krunner history is gone and keyboard's responding returns to normal.

P/S:
My problem is likely caused by ibus.