Bug 419400

Summary:	kscreenlocker lock screen "after waking from sleep" option does not work when using ConsoleKit2
Product:	[Unmaintained] kscreenlocker	Reporter:	Logan Rathbone <poprocks>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	bshah, kde, nate
Priority:	VLO
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Logan Rathbone 2020-03-29 23:19:43 UTC

SUMMARY

I am not sure why, as it used to work - but at some point in time, kscreenlocker's "Lock screen: after waking from sleep" option stopped working. Upon wake from sleep, the desktop simply resumes on my system, regardless of my settings.


EXPECTED RESULT

Settings should be honoured; screen should successfully lock upon resume if that is what my settings are.

SOFTWARE/OS VERSIONS

Linux

Operating System: Slackware Current (ktown; mostly vanilla builds)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2
Kernel Version: 4.14.59
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4710HQ CPU @ 2.50GHz
Memory: 7.7 GiB of RAM

kscreenlocker version:  5.18.3

ADDITIONAL INFORMATION

I am not running systemd. Perhaps that has something to do with it. Running ConsoleKit2 &c.

Contents of my ~/.config/kscreenlockerrc file:

***
[$Version]
update_info=kscreenlocker.upd:0.1-autolock

[Greeter]
Theme=org.kde.breeze.desktop

[Greeter][Wallpaper][org.kde.image][General]
Image=file:///usr/share/wallpapers/Next/contents/images/1366x768.png
***

I also tried manually adding:

[Daemon]
LockOnResume=true

to the configfile, and it made no difference.

Marking this as "major" as it has security (with a small "s") implications.

Comment 1 Nate Graham 2021-06-21 22:33:43 UTC

Hmm, works for me with systemd.

Note that consolekit is unmaintained. Does consolekit2 work better?

Comment 2 Logan Rathbone 2021-06-22 22:12:20 UTC

I was running this on ConsoleKit2.

Now that Slackware has migrated to elogind, I do not see this issue any longer.

Comment 3 Nate Graham 2021-06-22 22:37:34 UTC

Thanks for the info.

Comment 4 David Edmundson 2021-07-14 10:20:43 UTC

I don't think we can do much without some more information from a relevant user with something super old.

Marking as worksforme.