Bug 228190 - Battery property page does not update
Battery property page does not update
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: gnome-power-manager (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-11 02:12 EST by Andrew Bartlett
Modified: 2013-03-05 22:49 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-14 04:47:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Bartlett 2007-02-11 02:12:51 EST
Description of problem:
The properties of the battery do not get updated when the battery is being charged.

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


How reproducible:
Every time.

Steps to Reproduce:
1. On a battery powered laptop
2. Unplug power cable
3. Select battery properties from context menu
4. Watch for changes in the values
  
Actual results:
Values do not change

Expected results:
Values should change

Additional info:
The notification for 'you are not on battery power' does remove the properties
page, but without bug #228189 the 'fully charged' notification doesn't occour.  

Updates while charging/discharging is however what I want to see (but not
polling excessivly, that would be pointless and just chew power).
Comment 1 Richard Hughes 2007-02-11 05:42:45 EST
When you are not getting any gui updates, do you get data from "lshal -m"?
Comment 2 Bill Nottingham 2007-03-02 12:30:55 EST
Moving to 'devel' as discussed on
https://www.redhat.com/archives/fedora-devel-list/2007-March/msg00095.html.
Comment 3 Richard Hughes 2007-05-14 04:47:37 EDT
The battery property page has been removed in 2-18, and refactored to something
else. Closing UPSTREAM.

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