https://bugs.kde.org/show_bug.cgi?id=500478
--- Comment #2 from Fabian Blaese <fabian+kdeb...@blaese.de> --- The issue seems to be related to the fingerprint/fprintd integration. I can reproduce this issue by locking the screen once, unlocking it using the password (even though the fingerprint reader is active), and locking it again. If the screen is unlocked using the fingerprint reader, the issue does NOT appear. I assume that the issue is somehow related to leftovers of the previous fingerprint session. After waiting for the fingerprint session to time out (30s by default), or by stopping fprintd manually, kscreenlocker exits and leaves the session unlocked (!). I have not previously noticed this behavior, because I have significantly increased the fingerprint timeout duration. I am not sure how kscreenlocker_greet is invoked when locking the session with a Hotkey (Super + L), but to me it looks like kscreenlocker_greet isn't even started when locking for the second time, and the black screen is drawn by a different component. -- You are receiving this mail because: You are watching all bug changes.
