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

[Michael Biebl]

Am 22.05.20 um 12:19 schrieb Vincent Lefevre:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/15887
>

Thanks for forwarding this issue.

> On 2020-05-22 06:08:02 +0200, Michael Biebl wrote:
>> I can't reproduce the issue with those instructions.
>> Must be something specific to your hardware / software configuration.
>>
>> To further debug this yourself, you might try running logind manually.
>> Stop the running instance, then run
>> SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-logind
> 
> The running instance cannot be stopped as it is automatically
> restarted. 

This is strange. Something is triggering the start of systemd-logind
(via D-Bus most likely). My educated guess is, that it is actually this
process, which triggers the suspend, not logind itself.

Remember when I initially said, that logind provides the mechanism and
the policy is supposed to be proved by something else (usually the
desktop environment).

-------------- 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/20200522/98278e0e/attachment.sig>