Description of problem: HAL 0.5.8.1-5.fc6 badly evaluate the battery status in Acer Aspire 3003LMi. In the newer it was fixed, I've heard. http://bugzilla.gnome.org/show_bug.cgi?id=354757#c9 (ACPID info about battery is correct) You can see how gnome-power-manager, which has an info from hal, works here: http://picasaweb.google.com/wojtekjs/
I've explored the problem a bit and found that it's a problem with a low voltage (1 mV when bettery is used, 2 mV when charged), which is reported by battery. It looks like HAL uses this voltage to count battery.charge_level.current.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
It was fixed in the next release of Fedora.
(In reply to comment #3) > It was fixed in the next release of Fedora. Thank you for reporting that. I'm closing this issue as RESOLVED.