Worked with 5.4.3, but as of 5.5.0 (and 5.5.1), the screen remains unlocked after a suspend/resume cycle. I even went into settings and unchecked the box, applied, then re-checked it and applied again just in case the setting backend was out of sync. Reproducible: Always
I cannot reproduce this unfortunately. The screen locks fine both when suspending manually and when it auto-suspends after a period of inactivity.
Hmm. Perhaps it is a Gentoo packaging issue. I have confirmed with other Gentoo folks that they do have the issue. Has anything notable changed in terms of dependencies with the 5.5.x series? I know that Gentoo broke kscreenlocker out into its own package as of 5.5.0. Does this reflect an upstream refactor, or just Gentoo package management? Any hints are appreciated and I will take it up with Gentoo.
KScreenlocker has indeed been split into its own separate repository.
I should also add that I do not use systemd on the affected systems (I use openrc), did anything change in kscreenlocker that might be affected by this?
There we have the culprit. I'm sorry, we require logind or console kit 2 (or any other service that provides these dbus services) since 5.5.
No, OpenRC on Gentoo does indeed use Consolekit2-1.0.0, which was pulled in when I installed plasma-5.5.0. What else could I check?
Created attachment 96395 [details] attachment-23561-0.html Do screen locking in general works? Or just lock screen on resume is broken?
Good point. Screen locking works fine if I press CTRL-ALT-L. However, I noticed something else today which I didn't notice before because my screen usually blanks (or the machine hibernates) on this laptop before the 10minute screen locker timeout is reached. I set the screen locking timeout to 1 minute, and disabled power management so the screen would not blank. I waited 2 minutes and the screen did not lock on its own. Finally, if I manually do the following: qdbus org.kde.screensaver /ScreenSaver Lock The screen does lock.
Actually I'm not sure if the screenlocker supports Consolekit 2, PowerDevil does but locking on suspend has been moved to the screen locker. Should be trivial to add, however. Patches welcome :)
I would like to help, but would require some hand holding as I do not understand the design of the software. For instance, I see in the logind.cpp there are multiple references to falling back to Consolekit if logind is not available. Also, in ksldapp.cpp it seems to fallback to letting Solid send a signal if logind is not available. Was the implementation started, but not plumbed in? Or is this leftover from when it was broken out into its own package? If someone gives me step by step instructions of what needs to be done, I can take a crack at it. However, if it is trivial and just a matter of hooking up a few things it might be a waste of time explaining how to do vs just doing it.
Nevermind, KScreenLocker supports the ConsoleKit 2 DBus interface. Looks like bug in ConsoleKIt 2 then. Please head over to https://github.com/ConsoleKit2/ConsoleKit2/issues and file an issue there. Thanks!
Can do, but before I do, does this also explain the issue that plasma doesn't lock after setting a 1 minute timeout? Is that a totally different issue? Shall I file a new bug?
Oh, hmm, no, this is unrelated. Yes, please file a separate bug about this. It looks like something is broken on your system. :/
Upstream bug filed https://github.com/ConsoleKit2/ConsoleKit2/issues/56
In case anyone else hits this, it seemed to be a Gentoo specific issue for upgraded legacy installations. You can fix it by doing the following: emerge -1a upower This should replace the old power management package upower-pm-utils, which was a stopgap package the Gentoo folks created to side-step systemd a while back. Nowadays, you can (and should) use upower directly even on non-systemd installations. Hope this helps others struggling like I was.