Comment 29 for bug 1574120

The problem persists after sorting the oddity with the unity-settings-daemon, which appears to have been a one-off problem. (See bug #1577906 for more detail.)

Now I find that suspend only works if "HandleLidSwitchDocked=suspend" is in logind.conf.

Without that I return to the bug condition.

In the bug condition suspend works fine from the session indicator.

neilw@NWPS-LAP:~$ systemd-inhibit
     Who: neilw (UID 1000/neilw, PID 1558/unity-settings-)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

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

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

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

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

5 inhibitors listed.