https://bugs.kde.org/show_bug.cgi?id=500339
--- Comment #36 from Ardo Kirsipuu <ardo.kirsi...@gmail.com> --- (In reply to John Kizer from comment #33) > I was able to reproduce this consistently by trying to triage > https://bugs.kde.org/show_bug.cgi?id=505288 - letting the screen lock on its > own, then beginning to type my password on the lock screen right at the time > specified in the setting. > > For example, with that delay set to the default 5 seconds, if I make the > first keystroke at 5 seconds after the screen locks, then I observe this > behavior where password attempts aren't "responded" to. That seems to fit > with the observation in comment 24 that changing that setting to "require > password immediately" stops the issue from occurring? First of all, how do you manage to start typing exactly at the 5 second mark? Or what do you mean? If I have "Delay before password required" set to 5 seconds and hit any key before 5 seconds then the lock screen just goes away like expected (no actual lock); if I type the password after 5 seconds then it's the usual works 95% of the time and doesn't 5% of the time. Secondly, sorry to say, but even with "require password immediately" it does not work 5% of the time. Actually, most of my debugging was done with that setting, including the attached logs and screenshots by me. Don't know what you meant by a workaround, but at least this definitely isn't. Perhaps comment 24 and you are talking about some other bug than the OP and me? -- You are receiving this mail because: You are watching all bug changes.
