Am 05.11.22 um 17:34 schrieb Steve McIntyre:
Package: systemd
Version: 247.3-7+deb11u1
Severity: important

Hi!

I've deliberately configured systemd on my laptops to *not* suspend on
lid close, multiple years ago. I've noticed a few times over the last
couple of years that it will sometimes revert to suspending and then
stay with that unwanted behaviour. This is very frustrating.

I've never managed to work out what's happening here, but I think I
may have finally found a reliable trigger!

On a newly-booted system, everything works fine and lid-close causes a
lock. After I start a docker container on this machine, behaviour
changes and it switches to suspending instead. I've done this three
times just now and this behaviour is reliable.

I'm happy to help debug this, but I have no idea on where to start...

urgh, docker...

They are notorious for not playing nice when it comes to systemd and just doing their own thing.
Just curious, if you use podman, can you reproduce the issue?



Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to