https://bugs.kde.org/show_bug.cgi?id=505288
--- Comment #9 from Vartan <forums.basil...@passmail.net> --- The two relevant settings (I think) are these: 1. System Settings -> Screen Locking -> "Lock screen automatically" 2. System Settings -> Screen Locking -> "Delay before password required" I'll refer to these as settings as parameters p1 and p2, respectively. On my system, p1 is set to 10 minutes and p2 is set to 5 seconds, but I don't believe that the values are significant. I have experimented with various values, and I can still reproduce the bug. After the expiration of the period given by p1, the lock screen dialog appears. If I type my password and hit RETURN (or the right arrow) prior to the expiration of the period given by p2, the screen remains unlocked, and I can continue with my session. However, this does not always work correctly. When the bug appears, I remain locked out of my session indefinitely. I have tried waiting for several minutes to see if there is a timeout period; there is none that I've seen. Here's the detailed scenario: 1. The time period given my p1 expires. 2. The lock screen dialog appears. 3. I type my password and hit RETURN (or the right arrow) close to the expiration of the value given by p2. 4. The lock screen remains. Thereafter, the only way to unlock the screen is to do the following: 1. Select "Switch User" 2. Type my password in the text field and hit RETURN I believe there is a race condition between: 1. the screen locking that starts when p2 expires 2. the screen unlocking code that executes when I enter my password I have not looked at any code, but the race condition explanation makes sense to me intuitively. It seems that there is no proper locking of the screen lock state -- no proper mutex locking of the state, however that's implemented. -- You are receiving this mail because: You are watching all bug changes.
