After upgrading to KDE 4.11.2 in Kubuntu 13.10, the system started to automatically shutdown when on battery and one of the two batteries is low or dead even though the other battery is fine. Reproducible: Always Steps to Reproduce: 1. Have 2 batteries 2. Drain one Actual Results: System constantly shutsdown until plugged in or the dead battery is removed. Expected Results: The system does not shutdown just because one of the systems batteries is dead. This is a very frustrating, reoccurring bug with power management and it seems that the current system looks at batteries individually instead of working on a summation of all batteries attached to a system. Another way of testing this might be to use a laptop plugged into a UPS although I can't remember if the battery management system monitors those batteries or if it was just the gnome power manager version that did (wishlist item if KDE's doesn't).
Same here opensuse 12.3, kde 4.11.2, laptop Lenovo T430s. =(
I'm facing the same problem. KDE 4.11.2 on Gentoo Linux, kernel version = 3.11.6. The model is Lenovo w530 with an external second battery.
*** Bug 332906 has been marked as a duplicate of this bug. ***
*** Bug 334340 has been marked as a duplicate of this bug. ***
Maybe patch from review-request https://git.reviewboard.kde.org/r/118801/ does also fix this bug, can someone please test it?
Git commit 775a99e8bc1e9c5e277ff17a84a406227a5a32fb by Emmanuel Pescosta. Committed on 17/06/2014 at 15:35. Pushed by emmanuelp into branch 'KDE/4.11'. Consider additional batteries for power management (when the critical battery timer is running) After resuming from suspend, all batteries are added to powerdevil. When a battery, with charge lower or equal than the critical charge percentage is added, the critical battery timer will be started. In the current version the critical battery timeout can only be interrupted by plugging in AC. But if the system has more than one battery, the global charge percentage can be greater than the critical charge percentage and so the system shouldn't suspend. To achive this behaviour, we calculate the global charge percentage whenever a new battery was added and if the critical battery timer is running and the global charge is high enough, we stop the timer. Also we use the already calculated global charge percentage for the battery charge percentage notification instead of the charge of each individual battery. With this patch, the user can not only interrupt the critical timer by plugging in the AC but also by plugging in a new or additional battery (if the battery has enough charge). Note: The 30 sec timeout message will still popup. Tested with a Thinkpad T440s (two batteries) @Philipp Paris: Thanks for testing! Related: bug 329537 FIXED-IN: 4.11.11 REVIEW: 118801 M +13 -1 powerdevil/daemon/powerdevilcore.cpp http://commits.kde.org/kde-workspace/775a99e8bc1e9c5e277ff17a84a406227a5a32fb
Git commit dc6753889e0428c7e7072d5cb9ea2cd8be4340fa by Emmanuel Pescosta. Committed on 29/07/2014 at 19:48. Pushed by emmanuelp into branch 'master'. After resuming from suspend, all batteries are added to powerdevil. When a battery, with charge lower or equal than the critical charge percentage is added, the critical battery timer will be started. In the current version the critical battery timeout can only be interrupted by plugging in AC. But if the system has more than one battery, the global charge percentage can be greater than the critical charge percentage and so the system shouldn't suspend. To achive this behaviour, we calculate the global charge percentage whenever a new battery was added and if the critical battery timer is running and the global charge is high enough, we stop the timer. Also we use the already calculated global charge percentage for the battery charge percentage notification instead of the charge of each individual battery. With this patch, the user can not only interrupt the critical timer by plugging in the AC but also by plugging in a new or additional battery (if the battery has enough charge). Related: bug 337414, bug 329537 FIXED-IN: 5.1 M +24 -11 daemon/powerdevilcore.cpp M +6 -0 daemon/powerdevilcore.h http://commits.kde.org/powerdevil/dc6753889e0428c7e7072d5cb9ea2cd8be4340fa