[systemd-devel] Locking current session programmatically

[Kirill Elagin]

If you don't have a DE you don't have a session manager either, so
systemd-logind can't help you anyway.
Indeed, you should just run your screenlocker.


--
Кирилл Елагин


On Sun, Jun 29, 2014 at 9:57 AM, Ivan Shapovalov <intelfx100 at gmail.com>
wrote:

> >> 27 июня 2014 г., в 21:54, Lennart Poettering <lennart at poettering.net>
> написал(а):
> >>
> >> On Fri, 27.06.14 17:45, Ivan Shapovalov (intelfx100 at gmail.com) wrote:
> >>
> >> I want to lock my current session using a command-line tool (or a D-Bus
> call).
> >>
> >> The only apparent way to do this is `loginctl lock-session
> $XDG_SESSION_ID`.
> >> However, this results in an "Access denied" reply, which is somewhat
> strange
> >> (I expect to be able to lock my own session).
> >>
> >> Is this by design or a bug?
> >
> > Neither. Just missing functionality. I added this to the TODO list now.
> >
> >> In either case, is it possible to lock the current
> >> session?
> >
> > Well, not with logind, no. But you should be able to do it with GNOME's
> APIs.
> >
> > Lennart
> >
> > --
> > Lennart Poettering, Red Hat
>
> I've got a DE-less setup (a freestanding window manager). Should I just
> invoke whatever tool I use for screenlocking (i3lock in my case)?
>
> --
> Ivan Shapovalov / intelfx /
>
> (Sent from a phone. Havoc may be wreaked on the formatting.)
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140629/68708895/attachment.html>