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

[Michael Biebl]

Am 21.05.20 um 20:41 schrieb 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.
> 

My point is: Only if I stop systemd-inhibit, the system will suspend on
lid-close. As long as it is running, it does not.

But it might very well be, that I misunderstand what you are trying to
say. Please try to explain it better then, in more detail.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200521/1f0eb759/attachment.sig>