[Powerdevil] [Bug 364478] Power settings concerning lid state are ignored / overridden

[Bzzz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364478

--- Comment #2 from Bzzz <bzzz at gmx.net> ---
Well, it would be very helpful for a non-dev person to have something to check
on. "logind" isn't a separate package to examine, not a single executable,
doesn't have a manpage, synaptic doesn't find anything with logind in it, etc. 
systemd-logind as in the bug report also doesn't really pop up as executable as
well. So here's the locate output:

locate logind
/etc/systemd/logind.conf
/lib/systemd/systemd-logind
/lib/systemd/system/systemd-logind.service
/lib/systemd/system/multi-user.target.wants/systemd-logind.service
/usr/lib/libreoffice/share/config/soffice.cfg/uui/ui/logindialog.ui
/usr/share/man/man5/logind.conf.5.gz
/usr/share/man/man5/logind.conf.d.5.gz
/usr/share/man/man8/systemd-logind.8.gz
/usr/share/man/man8/systemd-logind.service.8.gz
/var/log/upstart/systemd-logind.log.1.gz
/var/log/upstart/systemd-logind.log.2.gz
/var/log/upstart/systemd-logind.log.3.gz
/var/log/upstart/systemd-logind.log.4.gz
/var/log/upstart/systemd-logind.log.5.gz
/var/log/upstart/systemd-logind.log.6.gz
/var/log/upstart/systemd-logind.log.7.gz

The gzipped log files are pretty empty (350B max @ 14d uptime and some more
power cycles) and especially without timestamps. 

I can however give the apt-show-versions systemd:
systemd:amd64/xenial-updates 229-4ubuntu6 uptodate
systemd:i386 not installed

kded5 run from console:
16:24:08:~$ kded5 
16:24:08:~$ 

Nothing else shows after closing and re-opening the lid.

I'll add an dbus-monitor dump from such a cycle as well. 

That aside: Doing a manual hibernation now doesn't work, instead the screen
lock applies and after unlocking a "Hey, someone else is logged in, now
hibernating does require root permission" popup is there. No other tty or
graphic session is active, though. All results from ps axo user |  sort -u are
system accounts plus this one that I'm using right now. So hibernating is
actually broken twice: It does when it shouldn't, and it doesn't when it
should.

-- 
You are receiving this mail because:
You are the assignee for the bug.