One other note, it appears that gsd-power might be blocking the suspend:

josh@josh-ThinkPad-T460 ~ systemd-inhibit
     Who: gdm (UID 147/gdm, PID 3040/gsd-power)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

     Who: NetworkManager (UID 0/root, PID 1524/NetworkManager)
    What: sleep
     Why: NetworkManager needs to turn off networks
    Mode: delay

     Who: josh (UID 1000/josh, PID 20754/gsd-power)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

     Who: gdm (UID 147/gdm, PID 3037/gsd-media-keys)
    What: sleep
     Why: GNOME handling keypresses
    Mode: delay

     Who: Telepathy (UID 1000/josh, PID 4930/mission-control)
    What: shutdown:sleep
     Why: Disconnecting IM accounts before suspend/shutdown...
    Mode: delay

     Who: josh (UID 1000/josh, PID 20754/gsd-power)
    What: handle-lid-switch
     Why: Multiple displays attached
    Mode: block

     Who: gdm (UID 147/gdm, PID 3040/gsd-power)
    What: handle-lid-switch
     Why: Multiple displays attached
    Mode: block

     Who: gdm (UID 147/gdm, PID 3037/gsd-media-keys)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

     Who: josh (UID 1000/josh, PID 20741/gsd-media-keys)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

     Who: UPower (UID 0/root, PID 2813/upowerd)
    What: sleep
     Why: Pause device polling
    Mode: delay

     Who: ModemManager (UID 0/root, PID 1466/ModemManager)
    What: sleep
     Why: ModemManager needs to reset devices
    Mode: delay

     Who: josh (UID 1000/josh, PID 20741/gsd-media-keys)
    What: sleep
     Why: GNOME handling keypresses
    Mode: delay

     Who: GNOME Shell (UID 1000/josh, PID 20651/gnome-shell)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

13 inhibitors listed.

And this related bug https://github.com/systemd/systemd/issues/7137


In the gnome power settings, on 16.04 there was a toggle to have it perform 
suspend with the lid closed while docked or while an external monitor was 
connected. That option is now gone. 

** Bug watch added: github.com/systemd/systemd/issues #7137
   https://github.com/systemd/systemd/issues/7137

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1574120

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to