For about two weeks now I've been using a secondary battery in my Thinkpad T61. Sometimes but not always when I resume from hibernation, KDE's powermanagement recognizes both batteries but still tells me my battery is run down to 0% and therefore goes back to hibernation within 30 seconds. Especially since my university studies just started today this really sucks. I haven't figured out yet under which circumstances powerdevil (or upower? don't know which one's responsible) recognizes the second battery and when it doesn't. The battery applet shows both batteries most of the time while it still sends my laptop to hibernation immediately saying "the" battery's run out of power. To complicate things further, sometimes the applet only shows the primary battery. When I plug in my laptop to the power outlet once after resuming, KDE's powermanagement behaves correctly even when I plug it off again. Possibly the bug really lies in the battery applet rather than the underlying powermanagement, but as I'm not sure I file it under powermanagement in general. Reproducible: Sometimes Steps to Reproduce: no exact steps to reproduce, see above /proc/version: Linux version 3.11.4-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Oct 5 21:22:51 CEST 2013
As I described on the Debian bugreport: http://bugs.debian.org/695966#10 I'm experiencing the same type of problems, namely: > With my Lenovo X220, when the additional battery is plugged in, the > internal battery drains first (that's the hardware managing the > drain-balancing I guess) and then PowerDevil insists to suspend the > laptop to disk (as I configured it to suspend-to-disk if there's less > than 4% of battery left). When waking up from suspend, powerdevil will > insist to suspend to disk again, no matter what the global battery state > is: > > $ acpitool > Battery #1 : Unknown, 0.00% > Battery #2 : Discharging, 54.94%, 02:31:00 > > (Applet shows 54%). > > This looks somewhat similar to [0]. As 'upower --dump' was requested, I > attached my output to this bugreport. > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=736835 I'm using KDE-Workspace 4.10.5 in Debian Jessie and would be very happy to help getting this solved, please ask! Cheers, OdyX
It seems to be the same bug: https://bugs.kde.org/show_bug.cgi?id=253453 There is a patch, but not upstream.
The patch mentioned in Comment #2 has been upstreamed.