https://bugs.kde.org/show_bug.cgi?id=505288

--- Comment #11 from Vartan <forums.basil...@passmail.net> ---
(In reply to John Kizer from comment #10)
> (In reply to Vartan from comment #9)
> > 3.  I type my password and hit RETURN (or the right arrow) close to the
> > expiration of the value given by p2.
> 
> It sounds like if you *start* typing your password after the "Delay before
> password required" has already been met - using your real-life settings as
> an example, 7 seconds after the screen locks automatically - then input is
> accepted into the password field but unlocking is impossible.
> 
> If you start typing your password *before* the "Delay before password
> required" has already been met - using your real-life settings, say at 3
> seconds after the screen locks automatically - does the lockscreen remain
> with input appearing in the password field, or does the lockscreen dismiss
> on the first keystroke?

I can reproduce the problem via either of these scenarios:
1.  I start typing my password 'just before' p2 expires.
2.  I start typing my password 'within some short time after' p2 expires.

In other words, 'just before' and 'within a short time after' are relatively
short delta time periods.  That is to say, I'm not waiting for 5 minutes after
the screen has locked to type my password to unlock the screen.  Nor am I
typing my password within 1 second of the time the lock screen appears (with
the password entry prompt). 

The time period is not exact, obviously.  But I will say that I specifically
try to achieve 1 and 2 above in order to test my theory that there is a race
condition.  For instance, I specifically ran the test where I start counting as
soon as the lock screen dialog appears (after expiration of p1).  I start
counting "one thousand one, one thousand two, one thousand three...) and when I
reach just before 5 seconds (using my settings) I start to type my password. 
Doing this I can reproduce the bug a fair percentage of the time.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to