Thanks for the quick answer Michael; I see logind suspending the system but not because of "System idle": I have then to investigate what component is triggering such suspend after a certain inactivity time. I guess this bug can be therefore closed.
Cheers, Andrea On Tue, Dec 7, 2021 at 11:55 AM Michael Biebl <[email protected]> wrote: > On 07.12.21 10:30, Michael Biebl wrote: > > Control: tags -1 + moreinfo > > > > On 07.12.21 09:47, Andrea V wrote: > >> changing IdleAction options inside /etc/systemd/logind.conf does not > >> have any effect on automatic sleep. > > > > What exactly does that mean? > > Do you want logind to suspend after some idle time (and it doesn't) or > > did you set IdleAction to ignore but it suspended anyway? > > Assuming it is the latter, keep in mind that IdleAction=ignore is the > default, so you don't need to explicitly configure it. > > I suspect that your system suspend wasn't actually trigged by logind's > idle action. > > But you can find out easily. > > Run (as root) journalctl -u systemd-logind and check the time window > when your system went into suspend. If it was triggered by logind, then > you should have a message like: > > > Dez 07 11:49:33 pluto systemd-logind[3087]: System idle. Doing suspend > operation. > Dez 07 11:49:33 pluto systemd-logind[3087]: Suspending... > > > >
