Description of problem: Very often, after I disconnect the AC from my Lenovo X201, the battery icon in the panel becomes immediately red and says 6.2% charge left. The remaining time, however is correct (2h40 left). The value slowly goes down as the battery discharges. So there seems to be an incorrect multiplication factor applied to the number. The command line tool acpi reports the correct percentage: bernie@giskard:~$ acpi Battery 0: Discharging, 59%, 02:46:56 remaining Version-Release number of selected component (if applicable): gnome-power-manager-2.32.0-3.fc14.x86_64 How reproducible: very often (always? not sure) Steps to Reproduce: 1.disconnect charger 2.look at battery icon Actual results: 5.7% Expected results: 56%
Same behavior here. My battery estimate is always off by a decimal place. it'll say 9.3% in the applet but the real battery life is 93% The time is right - but the battery icon is wrong and the percentage is wrong.
Can you test the kernel from http://koji.fedoraproject.org/koji/taskinfo?taskID=2686910 when it's built?
kernel-2.6.35.10-74.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.10-74.fc14
kernel-2.6.35.10-74.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/kernel-2.6.35.10-74.fc14
kernel-2.6.35.10-74.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 608341 has been marked as a duplicate of this bug. ***
I've still got this problem with Fedora 16 x64 (EFI boot) on a macbook pro 8,1. Sometimes the "energy when full" value in upower becomes much too large causing the battery to report a low percent. Time is still reasonable. Killing upowerd seems to fix the problem.
Sorry for the double post. Can this bug be reopened? Also I think the effected component should be upower not the kernel.
Dan, Please open a separate bug. You have similar symptoms, but if it was the same problem it'd already be fixed.