SUMMARY Sometimes I spam [FN] + [F3] often to increase the volume on my laptop. I don't keep it down, it is faster when pressing it multiple times. Sometimes the key then gets stuck and the volume is increased to the maximum value and I have to press the key again and then lower the volume again. I also experience it sometimes that the middle mouse button gets "stuck" and whatever button I press on my mouse, it results in the same as the middle key (when clicking on windows a new one opens) and I have to logout and login again. STEPS TO REPRODUCE Not quite sure, it is not happening always. But pretty much spam a key and hava a chance it stays pressed OBSERVED RESULT Don't get stuck SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION I know this is really hard to debug or reproduce, tell me what you need, I can (try) to give it to you.
I can trigger this "middle click" only in kde plasma (maybe other kde applications?), other applications (like chromium) are not affected. It just hit me after resuming from stand by.
This will be hard to reproduce as keys can occasionally get stuck even when they don't appear to be pressed, at least I've had such issues on other platforms, therefore while I may have been also affected, I never blamed this on KDE. Not sure if it's related, but I have a silly reproducer for getting a software stuck key: /bin/dbus-send --session --print-reply --dest=org.kde.kglobalaccel /component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut string:'Turn Off Screen' Initially used this avoid the shortcoming of the lock screen lingering around for too long without a shorter timeout, but I've noticed that I'm getting quite weird behavior after running this command. Realized that after pressing enter and the screen getting turned off, the key release event doesn't get processed, so enter keeps on being repeated until it's pressed again. In case anyone is interested in the purpose of command itself, it does work with "sleep 30 && " or something similar prefixed, also allowing locking before the screen gets turned off. The solution of bug 348529 obsoletes it though.