Bug#794744: systemd-logind: Lid closed event does not suspend

[Brian May]

On Thu, 6 Aug 2015 at 21:29 Michael Biebl <biebl at debian.org> wrote:

> Is another process blocking suspend?
> What's the output of systemd-inhibit?
>

 prune# systemd-inhibit
     Who: NetworkManager (UID 0/root, PID 535/NetworkManager)
    What: sleep
     Why: NetworkManager needs to turn off networks
    Mode: delay

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

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

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

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

5 inhibitors listed.



Can you add "systemd.log_level=debug" to the kernel command line, that
> should give you a more verbose log for systemd-logind.
>

That didn't seem to make any change. Wonder if it worked?

 prune# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.1.0-trunk-amd64
root=UUID=68f9ab76-d7fd-432a-9357-48dba9a8243b ro systemd.log_level=debug
quiet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150806/ed66006c/attachment-0002.html>