Am 16.08.2018 um 01:30 schrieb Christoph Anton Mitterer: > Thanks for the hints :-) > > On Thu, 2018-08-16 at 01:12 +0200, Michael Biebl wrote: >> 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. > > now before restarting logind the first time I had: > $ systemd-inhibit > Who: UPower (UID 0/root, PID 3801/upowerd) > What: sleep > Why: Pause device polling > Mode: delay > > Who: NetworkManager (UID 0/root, PID 4019/NetworkManager) > What: sleep > Why: NetworkManager needs to turn off networks > Mode: delay > > 2 inhibitors listed. > > > and afterwards, upower was gone > > > $ systemd-inhibit > Who: NetworkManager (UID 0/root, PID 4019/NetworkManager) > What: sleep > Why: NetworkManager needs to turn off networks > Mode: delay > > 1 inhibitors listed. > > > When I now restart upower.service it goes back into the list, but when > I now press the power button, I still get an immediate shutdown...
upower is a red herring. Please restart your desktop session and then run systemd-inhibit. -- 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
