#804434 gdm3: hangs when going to sleep due to low battery in laptop

Package:
gdm3
Source:
gdm3
Description:
GNOME Display Manager
Submitter:
Arturo Borrero Gonzalez
Date:
2015-11-08 12:39:05 UTC
Severity:
normal
#804434#5
Date:
2015-11-08 12:34:47 UTC
From:
To:
Dear maintainer,

my laptop was running out of battery and at some point it tried to go to sleep
automatically.

I'm using XFCE4. The window hanged and I had to manually reboot the machine
(using physical buttons).

Here are the only weird things I see in my logs:

[...]
Nov  8 13:18:16 debian kernel: [ 3665.334493] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Nov  8 13:18:16 debian kernel: [ 3665.334495] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Nov  8 13:18:16 debian NetworkManager[771]: <info>  (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Nov  8 13:18:16 debian dbus[741]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov  8 13:18:16 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov  8 13:18:16 debian NetworkManager[771]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Nov  8 13:18:16 debian dbus[741]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov  8 13:18:16 debian nm-dispatcher: Dispatching action 'down' for wlan0
Nov  8 13:18:16 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Nov  8 13:18:16 debian systemd[1]: Reached target Sleep.
Nov  8 13:18:16 debian systemd[1]: Starting Hibernate...
Nov  8 13:18:17 debian kernel: [ 3666.293561] PM: Hibernation mode set to 'platform'
Nov  8 13:18:17 debian systemd-sleep[24822]: Suspending system...
Nov  8 13:18:17 debian /etc/gdm3/Xsession[1876]: [2085:2301:1108/131817:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106
[...]

After these logs, it comes the new boot proccess.

I don't know if this bug belongs to gdm3 actually. Please reassign if neccesary.