Bug 317605 - low battery warning displayed even though second battery is full
Summary: low battery warning displayed even though second battery is full
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement (show other bugs)
Version: 4.10.1
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-30 13:41 UTC by Craig Magina
Modified: 2013-07-29 21:20 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screen shot (105.54 KB, image/jpeg)
2013-04-01 18:56 UTC, Scott Kitterman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Magina 2013-03-30 13:41:41 UTC
I have 2 batteries in my T410s and get low battery warnings even though only one of the two batteries is low.

Reproducible: Always

Steps to Reproduce:
1. Have one fully charged battery and one low battery.
2. Suspend the laptop.
3. Resume the laptop.
Actual Results:  
A low battery warning appears.

Expected Results:  
No low battery warning since the second battery is fine.
Comment 1 Scott Kitterman 2013-04-01 18:56:41 UTC
Created attachment 78549 [details]
screen shot

I see this also on 4.9.5 (it worked in 4.8, but I've never seen it work on 4.9 or later).  The attached screen shot shows battery 0 at 10% and battery 2 at 64% in upower --dump, but the battery widget says 10%.  I have "show the charge state for each battery present" selected and only battery 0 is showing.
Comment 2 Alex Fiestas 2013-04-02 19:54:00 UTC
Checked, second battery is not taken into account
Comment 3 Alex Fiestas 2013-07-28 22:12:30 UTC
Kai, this shouldn't happen anymore, right?
Comment 4 Kai Uwe Broulik 2013-07-29 13:26:46 UTC
Reading the code it shouldn't but that code hasn't really changed much. What I recently did was preventing it from notifying this way when eg. your mouse gets low.
PowerDevil adds up all the battery percentages and checkes whether the total is below the warning level.
Comment 5 Scott Kitterman 2013-07-29 17:45:03 UTC
Seems fine to me now in 4.10.5.
Comment 6 Alex Fiestas 2013-07-29 21:20:55 UTC
Original reporter has not said anything since bug was reported (a few month ago), issue got fixed for another user.

So I'm going to close the bug as resolved/fixed, if by any chance I'm wrong and it is not fixed in 4.10.5 or 4.11 please, feel free to reopen the bug.

Thanks for reporting !