Bug 425616 - kscreenlocker does not allow unlocking via screensaver interface
Summary: kscreenlocker does not allow unlocking via screensaver interface
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-20 20:18 UTC by Nicolas Fella
Modified: 2020-08-20 20:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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.