https://bugs.kde.org/show_bug.cgi?id=505288
John Kizer <john.ki...@proton.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
CC| |john.ki...@proton.me
Status|REPORTED |NEEDSINFO
--- Comment #8 from John Kizer <john.ki...@proton.me> ---
We're trying to pin down exactly what the sequence of user-facing or user-input
events, and timing of those events, is when you're seeing this issue. "Race
condition" would be a cause - it's important to be clear about the specific
symptoms first (somewhat related:
https://community.kde.org/Get_Involved/Issue_Reporting#Proposing_a_solution )
The thing that sticks out to me as surprising is that you mentioned "+/-" the
delay - using hypothetical numbers, are you saying that if you set a delay of 5
seconds after locking, but start typing your password at 4 seconds after
locking, the screen does not automatically unlock?
If so, that seems likely to be key to the issue, as that itself is unintended
behavior - the interaction of typing at 4 seconds after locking should
immediately unlock your device. If it only happens within a certain time range
after the delay period, but *not* before, that's helpful to know as well.
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
