Bug 1029627

Summary: Power management with multiple batteries broken
Product: [Fedora] Fedora Reporter: Amit Shah <amit.shah>
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: amit.shah, bnocera, fmuellner, mkasik, ofourdan, otaylor, pnemade, rstrode, samkraju, tiagomatos, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-18 18:41:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Image showing incorrect calculation for time remaining none

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.