I set my laptop to hibernate when battery reaches critical level (5%). However, this does not happen, and no warning is issued about having reached critical level, with the risk of draining and damaging the battery and losing data. Using Qt: 4.8.6 KDE Development Platform: 4.13.3 Plasma Desktop Shell: 4.11.11
Same thing here. It fails to hibernate when battery gets critical. Also missing are the notifications about battery levels, warning or critical. The only time it notices that it's critical is if I reboot the machine when critical only then once I log I get a popup in the screen top about batterly level being critical and system about to get hibernated soon, but if I plug the charger in and out there are no futher notifications of any kind and the system will run itself to 0% and shutdown abruptly. If I modify the low and critical levels to up and/or down only the screen brightness would seem to react, but no hibernation nor any notifications about being low or critical. Hibernation otherwise works ok with pm-hibernate. And the system does suspend after the timeout. It used to work ok. This regression came into picture this fall, probably at the switch to 4.14.1, but I'm not 100% sure. Using: kde 4.14.1 kernel 3.16.6-200-fc20 distro fedora 20
Hmm, this seems to have been resolved by removing ~/.kde/share/config/*power* files and thus restoring the defaults. There wasn't anything weird in them as far as I can tell. All small tweaks made using the pointy-clickety powermanagement gui. I still have the backups incase some is interested, just drop me an email.
Is your battery status being correctly reported? Could you compare battery status between upower -d and battery widget. I am seeing similar thing on Plasma 5. https://bugs.kde.org/show_bug.cgi?id=340964
Tommi Kyntola: > this seems to have been resolved by removing ~/.kde/share/config/*power* > files and thus restoring the defaults I tried by this didn't fix the problem for me. donniezazen: > Is your battery status being correctly reported? > Could you compare battery status between upower -d and battery widget. upower -d and the battery widget match. Just a thought, but couldn't this be due to systemd interfering in some way with power management?
(In reply to Tommi Kyntola from comment #2) > Hmm, this seems to have been resolved by removing > ~/.kde/share/config/*power* files and thus restoring the defaults. I had the same problem and this workaround helped me!
Hi, This bug should be marked as confirmed: I and a large number of other users have experienced it, as shown on the Debian bug tracker bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769155 There are fortunatelly a couple of other workarounds other than the one mentioned above. I can't vouch for any of them, but here they are, copy-pasted: "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" (quoted from https://bugs.debian.org/cgi-bin/bugrepo ... =769155#51) Option 2 Run systemctl enable upower . This option seems to have worked for me, although I haven't tested it fully. --- Also I wondered if the title of this bug report as the problem isn't specifically with it not hibernating; i think it also won't shutdown, etc., depending on user settings? Again, I can't confirm that. Thanks!
I am similarly suffering from this issue. Unfortunately, none of the workarounds have fixed anything
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham