After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 323186 - some ACPI laptops erroneously report a non-zero rate when on AC and fully charged
some ACPI laptops erroneously report a non-zero rate when on AC and fully cha...
Status: RESOLVED FIXED
Product: gnome-applets
Classification: Other
Component: battery
2.12.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-04 07:14 UTC by Adam Guthrie
Modified: 2005-12-11 08:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Adam Guthrie 2005-12-04 07:14:13 UTC
Distribution/Version: Ubuntu

After being out and about I plug my power cable back in and let my battery
recharge. After it's done recharging I can hover over it and it says: "Battery
charged (100%)", but it shows the time as something like "79:00".

I am using HAL according to the steps in the troubleshooting section of the help.

`cat /proc/acpi/battery/BAT0/state' shows:

present:                 yes
capacity state:          ok
charging state:          charged
present rate:            1 mA
remaining capacity:      4800 mAh
present voltage:         12584 mV

The only way I've found to fix this is to go to the preferences and change the
setting from time to percent, and then back again. I suppose restarting the
applet would fix it, too, but I've yet to try this.
Comment 1 Allison Karlitskaya (desrt) 2005-12-06 04:37:05 UTC
Interesting.  Your battery says that it's charged (ie: not charging or
discharging) yet still lists a charge/discharge rate (of 1 mA).

This is almost definitely the cause of your problems and is likely due to a
buggy ACPI implementation.  I'm not sure what we can do to fix this but I'll try
to keep it in mind next time I'm writing workaround code for weird ACPIs.
Comment 2 Allison Karlitskaya (desrt) 2005-12-11 08:53:23 UTC
I've just commited the fix that I showed you on IRC to upstream HAL CVS HEAD
(scheduled for release as 0.5.6).

This should fix your problem but if it doesn't then please reopen this bug.