Bug#1001263: logind: IdleAction=ignore not effective

[Andrea V]

Package: systemd
Version: 249.7-1
Severity: normal
X-Debbugs-Cc: andreak...@gmail.com

Dear Maintainer,

changing IdleAction options inside /etc/systemd/logind.conf does not
have any effect on automatic sleep. In addition, even specifying a
command that should explicitly prevent the system from going to sleep on
idle has also no effect:

# systemd-inhibit --what=idle bash -c 'sleep 99999999999'
# systemd-inhibit --list
WHO UID USER PID COMM WHAT WHY MODE
ModemManager 0 root 1213 ModemManager sleep ModemManager needs to reset devices delay
NetworkManager 0 root 1150 NetworkManager sleep NetworkManager needs to turn off networks delay
Unattended Upgrades Shutdown 0 root 1273 unattended-upgr shutdown Stop ongoing upgrades or perform upgrades before shutdown delay
bash -c sleep 99999999999 1000 karimo 2530 systemd-inhibit idle Unknown reason block

Bests!

-- Package-specific info:

-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.3.1-1
ii libapparmor1 3.0.3-6
ii libaudit1 1:3.0.6-1+b1
ii libblkid1 2.37.2-4
ii libc6 2.32-4
ii libcap2 1:2.44-1
ii libcrypt1 1:4.4.26-1
ii libcryptsetup12 2:2.4.2-1
ii libgcrypt20 1.9.4-4
ii libgnutls30 3.7.2-2
ii libgpg-error0 1.42-3
ii libip4tc2 1.8.7-1
ii libkmod2 29-1
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2
ii libmount1 2.37.2-4
ii libpam0g 1.4.0-10
ii libseccomp2 2.5.3-2
ii libselinux1 3.3-1+b1
ii libsystemd0 249.7-1
ii libzstd1 1.4.8+dfsg-3
ii mount 2.37.2-4
ii util-linux 2.37.2-4

Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.12.20-3
ii systemd-timesyncd [time-daemon] 249.7-1

Versions of packages systemd suggests:
ii policykit-1 0.105-31
pn systemd-container <none>

Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.140
ii libnss-systemd 249.7-1
ii libpam-systemd 249.7-1
ii udev 249.7-1

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
SystemMaxUse=5G

/etc/systemd/logind.conf changed:
[Login]
IdleAction=ignore
IdleActionSec=120min


-- no debconf information

[Michael Biebl]

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?

[Michael Biebl]

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...

[Andrea Villa]

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