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

[Luca Boccassi]

Control: close -1

On Fri, 22 May 2020 12:19:56 +0200 Vincent Lefevre <vincent at vinc17.net>
wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/15887
> 
> 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. I had to add "Environment=SYSTEMD_LOG_LEVEL=debug"
> to the [Service] section as explained here:
> 
>  
https://lists.freedesktop.org/archives/systemd-devel/2013-March/010004.html
> 
> > Maybe you find any clues what's going on your system.
> 
> I've reported the bug upstream with debug information. I've also
> attached the logs to this message.
> 
> But systemd-logind still does not explain *why* it is suspending
> the system. Before the VT change, I can see that systemd-logind
> takes the inhibitor into account ("Refusing suspend operation,
> handle-lid-switch is inhibited"). And just after the VT change,
> it suspends the system.

As explained in the upstream ticket, this is mostly a misunderstanding
and a documentation issue, closing.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240527/755c5fd6/attachment-0001.sig>