I am working on an app that is able to remotely lock the screen of a user. case: you forgot to lock your desktop when you went for lunch/coffee and want to make sure your laptop is locked.
Different desktop environments have different service names to lock the screen:
on KDE: org.kde.screensaver
on Unity and GNOME: org.gnome.ScreenSaver
Regarding path:
on KDE and GNOME: /ScreenSaver
on Unity: /com/canonical/Unity/Session
Thank you, we will investigate the security impact of the interface and either add this to one of the existing interfaces or create a new, dedicated interface.
We already have âscreen-inhibit-controlâ in a separate interface, which I think is correct because a snap could inhibit screenlocking and expose users to risk. It makes some sense to then have a corresponding screen-lock interface, but because screen locking actually makes things more secure and we would allow auto-connection, I think it makes more sense to simply add to the desktop interface. Weâll try to get this into 2.30.
These are both committed. Please test the 2.30 core snap when it hits candidate (or test newer versions that have the change in edge/beta) and comment if it doesnât work for you.