[systemd-devel] Why is my docked idle laptop suspended?

[Lennart Poettering]

On Thu, 13.08.15 22:53, Michal Sojka (sojkam1 at fel.cvut.cz) wrote:

> Hi list,
> 
> I'm trying to figure out why is my laptop automatically suspended after
> being idle in a docking station. As far as I understand, logind should
> not suspend when the laptop is docked or external monitor is connected.
> 
> Below is the (partially filtered) system log of what happens before the
> suspend. Things start at 17:34:09 when my screensaver sets IdleHint. Few
> minutes later (17:37) something happens and the logind suspends the
> system. I don't expect that network manager, active at the same time,
> can cause this.
> 
> When looking at function manager_is_docked_or_external_displays(), when
> my system is docked, I should see "System is docked." message, but
> instead I see "External (1) displays connected." Can it be that the
> monitor powers down automatically and logind suspends the system because
> it is not aware of being docked?

Note that systemd will print "System is docked" only if there's an
actual "docking" state known, i.e. via some input device that is
connected to the hinge of your laptop. Most laptops don't expose
this. In that case we count external displays, and then you only see
the "External displays connected" message, instead.

Which version of systemd are you running?

Maybe some other usperspace service is triggering the suspend?

> 
> If yes, how can I make logind be aware of being docked?
> 
> Thank you.
> -Michal
> 
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Got message type=method_call sender=:1.39 destination=:1.224 object=/org/freedesktop/login1/session/_32 interface=org.freedesktop.login1.Session member=SetIdleHint cookie=34 reply_cookie=0 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=3105 reply_cookie=0 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.224 object=n/a interface=n/a member=n/a cookie=2170 reply_cookie=3105 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/login1/session/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=3106 reply_cookie=0 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=3107 reply_cookie=0 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/login1/user/_1000 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=3108 reply_cookie=0 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=3109 reply_cookie=0 error=n/a
> Aug 13 17:34:09 steelpick systemd-logind[16201]: device-enumerator: scan all dirs
> Aug 13 17:34:09 steelpick systemd-logind[16201]:   device-enumerator: scanning /sys/bus
> Aug 13 17:34:09 steelpick systemd-logind[16201]:   device-enumerator: scanning /sys/class
> Aug 13 17:34:09 steelpick systemd-logind[16201]: External (1) displays connected.
> Aug 13 17:34:09 steelpick systemd-logind[16201]: Refusing operation, as it is turned off.
> ...

I'd would be nice to see what's going on here...

> Aug 13 17:37:48 steelpick NetworkManager[1420]: <info>  (wlan0): DHCPv4 state changed bound -> bound
> Aug 13 17:37:48 steelpick NetworkManager[1420]: <warn>  (wlan0): Lowering IPv6 MTU (1280) to match device MTU (0)
> Aug 13 17:37:48 steelpick NetworkManager[1420]: <warn>  (wlan0): IPv6 MTU (0) smaller than 1280, adjusting
> Aug 13 17:37:48 steelpick NetworkManager[1420]: <warn>  (wlan0): Raising device MTU (0) to match IPv6 MTU (1280)
> Aug 13 17:37:48 steelpick dbus[1307]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
> Aug 13 17:37:48 steelpick dhclient[22949]: bound to 147.32.219.249 -- renewal in 261 seconds.
> Aug 13 17:37:48 steelpick systemd[1]: Starting Network Manager Script Dispatcher Service...
> Aug 13 17:37:48 steelpick systemd-logind[16201]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/NetworkManager_2ddispatcher_2eservice interface=org.freedesktop.DBus.Properties member=P
> Aug 13 17:37:48 steelpick NetworkManager[1420]: <info>  sleep requested (sleeping: no  enabled: yes)
> Aug 13 17:37:48 steelpick systemd-logind[16201]: device-enumerator: scan all dirs
> Aug 13 17:37:48 steelpick NetworkManager[1420]: <info>  sleeping...
> Aug 13 17:37:48 steelpick systemd-logind[16201]:   device-enumerator: scanning /sys/bus
> Aug 13 17:37:48 steelpick NetworkManager[1420]: <info>  (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
> Aug 13 17:37:48 steelpick systemd-logind[16201]:   device-enumerator: scanning /sys/class
> Aug 13 17:37:48 steelpick systemd-logind[16201]: Failed to open configuration file '/etc/systemd/sleep.conf': No such file or directory
> Aug 13 17:37:48 steelpick systemd-logind[16201]: Suspending...
> ...

Lennart

-- 
Lennart Poettering, Red Hat