Bug 443069 - constant 0 line in power history on AC
Summary: constant 0 line in power history on AC
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 446754 (view as bug list)
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
 
Reported: 2008-04-18 14:11 UTC by Matthias Clasen
Modified: 2008-09-10 12:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-10 12:46:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthias Clasen 2008-04-18 14:11:30 UTC
My computer seems to use no power at all when on AC, or so gnome-power-manager
wants me to believe.

Richard said that this might be the kernel using '0' when it means 'no idea'.

Comment 1 Richard Hughes 2008-04-18 15:09:31 UTC
Can you try the rawhide gnome-power-manager rpm here pls:
http://people.freedesktop.org/~hughsient/fedora/9/i386/

Thanks.

Comment 2 Matthias Clasen 2008-04-18 16:31:38 UTC
I would, but 

error: unpacking of archive failed on file
/usr/share/gnome-power-manager/gpm-suspend-failure.wav;4808cc8a: cpio: MD5 sum
mismatch


gpk-install-file did not warn me about that, btw

Comment 3 Bug Zapper 2008-05-14 09:38:55 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Matthias Clasen 2008-05-19 20:38:48 UTC
*** Bug 446754 has been marked as a duplicate of this bug. ***

Comment 5 Richard Hughes 2008-09-10 12:46:50 UTC
Right, if you are on AC power and your battery is fully charged, then we can't get any power information from the battery at all. You can't represent "no data" in this version of g-p-m, although I'm made sure this is possible in DeviceKit power, and the next version of gnome-power-manager.


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