rb@bluejay:~/git/mps/code$ systemd-inhibit
     Who: NetworkManager (UID 0/root, PID 812/NetworkManager)
    What: sleep
     Why: NetworkManager needs to turn off networks
    Mode: delay

     Who: rb (UID 1000/rb, PID 1589/unity-settings-)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

     Who: rb (UID 1000/rb, PID 1589/unity-settings-)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

     Who: Unity (UID 1000/rb, PID 1594/compiz)
    What: sleep
     Why: Unity needs to lock the screen
    Mode: delay

4 inhibitors listed.

Note: Closing the lid does switch off the display, but doesn't suspend
the machine.

Here is the tail of the output of journalctl at the time I closed and
opened the lid.

Apr 26 23:21:13 bluejay kernel: atkbd serio0: Unknown key pressed (translated 
set 2, code 0xd8 on isa0060/serio0).
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' 
to make it known.
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Unknown key released (translated 
set 2, code 0xd8 on isa0060/serio0).
Apr 26 23:21:13 bluejay kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' 
to make it known.
Apr 26 23:21:14 bluejay systemd-logind[828]: Lid closed.
Apr 26 23:21:17 bluejay systemd-logind[828]: Lid opened.
Apr 26 23:21:22 bluejay sudo[8534]:       rb : TTY=pts/6 ; 
PWD=/home/rb/git/mps/code ; USER=root ; COMMAND=/bin/journalctl -b
Apr 26 23:21:22 bluejay sudo[8534]: pam_unix(sudo:session): session opened for 
user root by (uid=0)

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to