Am 16.08.2018 um 01:05 schrieb Michael Biebl: > Am 15.08.2018 um 23:32 schrieb Christoph Anton Mitterer: >> I'm afraid, I have no idea why mine doesn't restart ^^ > > In any case, this looks like a cinnamon issue. > My guess is, that the cinnamon component responsible for power > management not deal with the fact that logind goes away and does not > re-connect when it shows up again. > > It's the responsibility of the DE to establish an inhibitor lock if it > wants to delay/block suspend/hibernate events.
Fwiw, you can check that by calling systemd-inhibit
This should show you which process holds a blocking inhibitor for the
key events. Under GNOME you'll have
Who: michael (UID 1000/michael, PID 5201/gsd-media-keys)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
Why: GNOME handling keypresses
Mode: block
Who: GNOME Shell (UID 1000/michael, PID 5036/gnome-shell)
What: sleep
Why: GNOME muss den Bildschirm sperren
Mode: delay
Restart logind, then check logind again.
If the process is no longer listed, file a bug report against the binary
which was running that process.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
