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

[Vincent Lefevre]

On 2020-05-21 20:38:16 +0200, Michael Biebl wrote:
> Am 21.05.20 um 00:26 schrieb 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).
> 
> fwiw, I can't reproduce this.
> What I tried:
> login on tty1, run systemd-inhibit
> switch to tty2, close the lid -> no suspend
> switch to tty1, kill systemd-inhibit
> switch to tty2, close the lid -> suspend

You did not understand. I do *not* kill systemd-inhibit.
But the system got suspended.

-- 
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)