Summary: | Some keys get stuck | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Moritz <bixilon> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | bixilon, nate, voidpointertonull+bugskdeorg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Moritz
2023-05-09 16:22:20 UTC
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. |