SUMMARY No matter how the screen lock is triggered (either by timeout or resuming from suspend), it sometimes appears immediately again after unlocking. STEPS TO REPRODUCE There is no stable way to reproduce, it just happens randomly. 1. Lock screen (by timeout or resuming from suspend) 2. Input password to unlock OBSERVED RESULT Sometimes the screen is immediately locked again. EXPECTED RESULT The screen is unlocked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 This issue is also seen on 5.14.*. ADDITIONAL INFORMATION
Here are some logs that appeared when this issue last happened: Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: Qt: Session management error: networkIdsList argument is NULL Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: UdevQt: unable to create udev monitor connection Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/WallpaperFader.qml:138:13: QML PropertyChanges: Cannot assign to non-existent property "opacity" Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Clock.qml:40:13: Unable to assign [undefined] to QColor Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Clock.qml:39:13: Unable to assign [undefined] to int Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Clock.qml:47:13: Unable to assign [undefined] to QColor Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Clock.qml:46:13: Unable to assign [undefined] to int Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:166: ReferenceError: clockShadow is not defined Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:174: ReferenceError: ColorScope is not defined Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:161:9: Unable to assign [undefined] to QColor Feb 15 17:29:20 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:160:9: Unable to assign [undefined] to int Feb 15 17:31:20 hostname kscreenlocker_greet[13859]: couldn't lock local file Feb 15 17:37:37 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/WallpaperFader.qml:119:13: QML PropertyChanges: Cannot assign to non-existent property "opacity" Feb 15 17:37:47 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/WallpaperFader.qml:138:13: QML PropertyChanges: Cannot assign to non-existent property "opacity" Feb 15 17:37:54 hostname kscreenlocker_greet[13859]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/WallpaperFader.qml:119:13: QML PropertyChanges: Cannot assign to non-existent property "opacity"
This bug is over a year old, but I had not seen it in that year despite keeping relatively up to date. I have now updated to Plasma 5.18.2, and now this happens quite often. I've generally noticed the behaviour after suspending, but it is not reproducible after a short suspend. There may be a time factor involved. Possibly relevant: the first unlock screen has the user picture enclosed and cropped in a circle; the second does not. Perhaps the behaviour is caused by a bug in the lock screen theme. I'll see if I can test that; I was using "Breeze for openSUSE".
I have not seen this issue happen for a long time. Can other subscribers also confirm?
Ok, lets close it can always be reopened. There isn't enough information to active work on it in the current state without it being reproducible