You are not logged in.
I am running Gnome3/GDM. If I do:
$ systemctl suspend
the screen goes blank, I hear the hard disk make a click sound, and then I'm back on the GDM login view. Nothing useful shows up in dmesg or journalctl between sleeping and waking.
After trying many things, I found that the following works:
$ rfkill block all
$ systemctl suspend
which causes the computer to go to sleep. I cannot wake it up with my (wireless) keyboard or mouse, but I can by pressing the power button. Blocking only bluetooth does NOT allow me to suspend
$ rfkill list
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
20: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ rfkill block 1
$ systemctl suspend # doesn't work immediately, works if I wait a while
$ rfkill unblock 1
$ rfkill block 20
$ systemctl suspend # doesn't work even if I wait
$ rfkill block 1
$ systemctl suspend # works if I wait a while
$ rfkill block all
$ systemctl suspend # works!
Why do I have to block wlan to get suspend to work?
Last edited by lumeno (2017-01-20 06:27:58)
Offline
your can try to set
SuspendKeyIgnoreInhibited=yes
in your /etc/systemd/logind.conf
This will make suspend unstoppable. There is a similar option for hibernation.
Offline
I got the same issue few time lately.
I'll try your solution next time it happens.
Also, I got this in my logs at boot that might be related:
janv. 17 17:35:16 some-laptop systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
janv. 17 17:35:16 some-laptop systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Offline
your can try to set
SuspendKeyIgnoreInhibited=yes
in your /etc/systemd/logind.conf
This will make suspend unstoppable. There is a similar option for hibernation.
I did this and rebooted and try to suspend again. It didn't help, it wakes up immediately.
Offline
@n0vember it seems that SuspendKeyIgnoreInhibited=yes just prevents to ignore the suspend key press event https://www.freedesktop.org/software/sy … .conf.html
Where did you find that it does more?
So I tried SuspendKeyIgnoreInhibited=yes and suspending still fails.
And `rfkill block all`didn't work either although it worked for @lumeno
Offline