Bug 454328

Summary: Can't type password immediately, keystrokes "get eaten" otherwise
Product: [Unmaintained] kscreenlocker Reporter: retired <pepko94>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bshah, nate, pepko94
Priority: NOR    
Version First Reported In: 5.24.90   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description retired 2022-05-24 11:06:21 UTC
SUMMARY
It appears that in 5.25 beta lockscreen was given some overhaul. Before that I was able to type in my password and press enter even if screen was displaying clock. Now it ignores keys until password field starts showing.

Is that intended behavior? I would assume in the name of "security" if true.
Now if it's intended, may I suggest doing it like Microsoft and asking user to press Enter, or do a swipe up gesture before password could be inserted? Otherwise it's just looks like UI is lagging from my perspective.

STEPS TO REPRODUCE
1.  Lock screen
2.  Start typing
3.  Keys are being ignored until lockscreen displays password field

OBSERVED RESULT
Can't type my password from muscle memory, unless I want to see "password incorrect" answer.

EXPECTED RESULT

Screenlocker should parse input as before.


Operating System: Arch Linux
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3720QM CPU @ 2.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Comment 1 Nate Graham 2022-05-24 16:58:18 UTC

*** This bug has been marked as a duplicate of bug 454108 ***