Page MenuHomeSolus

Suspend doesn't work after 1.2.05 on XPS9350
Closed, InvalidPublic


After updating to 1.2.05 my computer doesn't suspend, instead just shuts down. This happens in multiple ways - eg computer is set to automatically suspend after an hour's inactivity but turns off. Power button programmed to suspend when pressed, shuts down as well. Closing the laptop will shut down computer instead of suspend. This is on a Dell XPS 9350, and didn't seem to happen at all until this recent update.

Event Timeline

Unknown Object (User) created this task.Sep 9 2016, 2:33 PM
JoshStrobl triaged this task as High priority.Sep 10 2016, 2:16 PM
JoshStrobl added a project: Hardware.

Just to be sure: in power settings, there is an option at the bottom that says "When the Power Button is Pressed". That's not set to "Hibernate" by chance, is it?

Unknown Object (User) added a comment.Sep 10 2016, 11:18 PM

Nope, definitely says "Suspend".

kirked added a subscriber: kirked.Sep 11 2016, 6:36 AM

Hmm, I'm definitely not seeing this behavior on a clean install on a XPS13 9350. Suspend works as expected for me.

I just installed today (Sat Sep 10) version

I would like to amend my comment above, as I've done more testing of this issue. I usually use my laptop plugged-in to provide more battery life.

My Settings:

Privacy: Auto Screen Lock, after blank for: Screen Turns Off
Power: Automatic Suspend: On, When the Power button is pressed: Suspend

Behavior while plugged-In:

  • Suspend via laptop lid OR power button: properly suspends, but DOES NOT engage the lock screen as it should.
  • Suspend via system menu: properly suspends, engaging the lock screen.
  • In both of these cases, if the power cord is removed, the system shuts down.

Behavior while on battery:

  • Regardless of the method of suspension, the system shuts down.

I can confirm this on a XPS15 9550

cyberdwarf added a comment.EditedNov 19 2016, 4:02 AM

Some more informations:

$ sudo journalctl | grep -C 3 "Lid opened"

Nov 19 04:41:34 steamer wpa_supplicant[692]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Nov 19 04:41:35 steamer systemd-logind[613]: Lid closed.
Nov 19 04:41:35 steamer systemd-logind[613]: Locking sessions...
Nov 19 04:41:40 steamer systemd-logind[613]: Lid opened.
Nov 19 04:41:44 steamer gnome-screensaver-dialog[2114]: gkr-pam: unlocked login keyring


#  This file is part of systemd.
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
# You can override the directives in this file by creating files in
# /etc/systemd/logind.conf.d/*.conf.
# See logind.conf(5) for details

cyberdwarf added a comment.EditedNov 19 2016, 12:24 PM

Just made some tests in other distros:

  • Linux Mint 18: Is suspending + /etc/systemd/logind.conf got only some properties set to "ignore"
  • Solus 1.2.1: Booted from USB, is not suspending
  • Ubuntu Gnome 17.04 dev-image: Booted from USB, is suspending + + /etc/systemd/logind.conf contains only comments (nothing is active). As far is I saw its Gnome 3.22. Also there were more options available in gnome-tweak-tool e.g. "on lid is close -> suspend" (screenshot wanted?)

Also I google the last hours a lot: As it looks to me many users (arch, ubuntu-gnome, gnome) got this problem after Gnome 3.20. I don't know if it helps but Ubuntu wrote a patch. Maybe some place to look it up? Ubuntu gnome-settings-daemon notes

cyberdwarf added a comment.EditedNov 19 2016, 1:20 PM

If I change my Gnome settings to go to suspend on pressing the power button it will suspend but not locking my session!

Only clicking at the suspend entry in the user indicator suspends correctly and locks the user session.

Just wrote this down to show, that suspense generally is working.

Also adding my inhibitors here:

     Who: cyberdwarf (UID 1000/cyberdwarf, PID 865/gnome-settings-)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

     Who: cyberdwarf (UID 1000/cyberdwarf, PID 865/gnome-settings-)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

     Who: NetworkManager (UID 0/root, PID 611/NetworkManager)
    What: sleep
     Why: NetworkManager muss Netzwerke abschalten
    Mode: delay

3 inhibitors listed.

In case I could to anything more here, please let me know!

cyberdwarf added a comment.EditedNov 23 2016, 9:05 PM

I set up Solus a few times the last hours and I discovered something interesting. Maybe its due to chance, but if i reboot I can not suspend directly after the system is back. BUT: A few minutes later (starting Chrome and browsed a bit) my XPS did suspend after I closed the lid..... --> but does not lock the screen
dmesg/journal looked like the would completely ignore a closed lid directly after a reboot.


I got different behavior in different BIOS versions. At the moment I run a 1.1.9 (because of ACPI-problems and screen flickering). Its highly possible that this issue cause thanks to Dells understanding in writing BIOS firmware (every update a new issue).

I can confirm that one. Closing the lid right after boot doesn't lock the screen and suspend. The ACPI events shows lid closed/open but it stays unlocked/awake.

Does anybody have any idea what might be causing this and why suspend still works on other distributions such as Ubuntu and Fedora but not Solus? I am also having this problem on an XPS 13.

JoshStrobl moved this task from Backlog to Other on the Hardware board.Oct 26 2017, 2:46 AM
JoshStrobl added a subscriber: JoshStrobl.

Does this issue still persist under a fully upgraded Solus 3?

DataDrake closed this task as Invalid.Mar 18 2018, 8:12 PM

Closing due to lack of response in over 30 days.