Bug#961146: systemd-logind sometimes ignores a systemd-inhibit lock

[Vincent Lefevre]

The suspend also occurs if I switch to a VT.

So it seems that if a "block" was triggered, it is cancelled once
the login session that started it is no longer associated with the
screen (something like that).

This would explain the issue I had with light-locker / lightdm
(bug 961124), because this is exactly this case.

The systemd-inhibit(1) man page says:

  --mode=
      Takes either "block" or "delay" and describes how the lock is
      applied. If "block" is used (the default), the lock prohibits any
      of the requested operations without time limit, and only privileged
      users may override it. If "delay" is used, the lock can only delay
      the requested operations for a limited time. If the time elapses,
      the lock is ignored and the operation executed. The time limit may
      be specified in logind.conf(5). Note that "delay" is only available
      for "sleep" and "shutdown".

So "without time limit", and I can't see any override in my case.

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)