I can confirm that starting upower before the KDE session makes everything work as expected. As a workaround, I am currently using the /etc/rc.local script to start upower with systemctl, as Andreas pointed out:
1) Make the /etc/rc.local script executable with: sudo chmod +x /etc/rc.local 2) Edit the file and add this line before the "exit 0" one: systemctl start upower I walked trough the kde-workspace-bin debian source, and seems like PowerDevil launches the upower service via DBus if it is not running, but I was unable to find out why the thread that monitors the battery level change don't work properly in some cases. It looks like some hardware specific information from the battery may cause be the issue, i.e., when upower starts from PowerDevil, it may not work as expected and the thread don't start properly. The weirdiest thing is that the battery icon *does* work, i.e., it shows the proper level; only the low/critical actions aren't triggered. I do agree, however, that the issue seems to be hardware specific, since it don't happen with most users, but it should be put in a wiki/errata so people can actually find the workaround for it. Em sáb, 7 de mar de 2015 às 22:57, Andreas Stempfhuber < reportbug2...@afulinux.de> escreveu: > Hi Stuart, > > I got a bit closer, when I start upower (using "systemctl start upower") > before I login on KDM then everything works! > > Unfortunately I'm not such familiar with systemd yet, how is it supposed to > work, when should /usr/lib/upower/upowerd get started? > > Thanks > > Andreas > > -- > To unsubscribe, send mail to 769155-unsubscr...@bugs.debian.org. >
