Bug 425616

Summary:	kscreenlocker does not allow unlocking via screensaver interface
Product:	[Plasma] kscreenlocker	Reporter:	Nicolas Fella <nicolas.fella>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	bhush94, kde
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nicolas Fella 2020-08-20 20:18:11 UTC

Running

qdbus org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver org.freedesktop.ScreenSaver.SetActive false

does not unlock the screen.

This seems to be a deliberate decision (https://invent.kde.org/plasma/kscreenlocker/-/blob/master/interface.cpp#L117).

It is however possible to unlock a session via logind, which makes this restriction rather pointless.

Comment 1 Kai Uwe Broulik 2020-08-20 20:40:35 UTC

It's not pointless. logind is a privileged process on the system bus, so we know it's coming from there. ScreenSaver on the other hand is a user service that anyone could just claim and tell us to unlock.