Bug 1029627 - Power management with multiple batteries broken
Summary: Power management with multiple batteries broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-12 19:05 UTC by Amit Shah
Modified: 2013-11-18 18:41 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-18 18:41:44 UTC
Type: Bug


Attachments (Terms of Use)
Image showing incorrect calculation for time remaining (77.06 KB, image/png)
2013-11-12 19:05 UTC, Amit Shah
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 712266 0 None None None Never

Description Amit Shah 2013-11-12 19:05:37 UTC
Created attachment 823105 [details]
Image showing incorrect calculation for time remaining

Description of problem:

I have two batteries on my ThinkPad 420s.  One is a 6-cell and the other is a 3-cell.  The laptop firmware discharges the 3-cell one completely before switching to the 6-cell one.  When the 3-cell one nears full discharge, gnome thinks the laptop is going to run out of power.

As shown in the attachment, the % remaining calculation is correct, and takes both batteries into account.  But the time remaining estimate is incorrect, and only based on the currently-discharging battery.

So gnome keeps suspending my laptop till the firmware switches to the 6-cell battery.

Once that happens, the time remaining is updated to reflect the 6-cell battery's discharge rate.

This is a regression from F19.


Version-Release number of selected component (if applicable):

$ rpm -q gnome-shell
gnome-shell-3.10.1-2.fc20.x86_64

Comment 1 Amit Shah 2013-11-18 18:41:44 UTC
gnome-settings-daemon-3.10.2 fixes this.


Note You need to log in before you can comment on or make changes to this bug.