Created attachment 128182 [details] My ~/.config/kscreenlockerrc SUMMARY When resuming from suspend I'm often unable to unlock the screen because there is no password prompt. STEPS TO REPRODUCE 1. Suspend at evening 2. Resume at morning OBSERVED RESULT There is no password unlock prompt, also time and date display are absent, only background image is visible. Mouse/touchpad and keyboard presses have no effects. Unable to unlock. EXPECTED RESULT Get a password prompt to type password and unlock the screen. SOFTWARE/OS VERSIONS The distribution is openmamba (it's missing in platform list, can it be added?) and I'm the RPM packages maintainer. Linux/KDE Plasma: KDE Plasma Version: any version tested in last years KDE Frameworks Version: any version tested in last years Qt Version: any version tested in last years ADDITIONAL INFORMATION To unlock I need to press CTRL-ALT-F2, login and kill the kscreenlocker_greet process. Then when going back with ALT-F1 i get the password prompt (a new kscreenlocker_greet process is spawned). It seems I can't reproduce the problem if I suspend/resume within a short time and also normal screen lock when PC is left on seems to always work. I've been having this problem for years about every two mornings. A similar bug has been closed in NEEDSINFO state, but I can give mode details as requested.
Are you using the Breeze theme? Seems like maybe an issue with the login screen theme itself. Can you see any QML errors on the console?
(In reply to Nate Graham from comment #1) > Are you using the Breeze theme? Seems like maybe an issue with the login > screen theme itself. Can you see any QML errors on the console? Yes it's Breeze. There are some QML errors, but don't know if they are relevant. I'm attaching parts of journal I saved some days ago when the problem happened.
Created attachment 128236 [details] Journal log around resume with screen unlockable
Thanks for the info. Nothing sticks out at me there.
*** This bug has been marked as a duplicate of bug 419142 ***
*** This bug has been marked as a duplicate of bug 370676 ***