https://bugs.kde.org/show_bug.cgi?id=469538
Pedro V <voidpointertonull+bugskde...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |voidpointertonull+bugskdeor
| |g...@gmail.com
--- Comment #2 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
