Description of problem: Upower shows the currenty percentage charge as 1/10th of the actual battery charge state. This inconsistency normally occurs after a suspend resume cycle. Version-Release number of selected component (if applicable): 0.9.17 How reproducible: Always Steps to Reproduce: 1. Charge / discharge laptop battery 2. Suspend and resume 3. Check upower -d Actual results: upower shows: Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0 vendor: SMPNz451948DGDLAM002ATL model: bq20z451948DGDLAM002ATL power supply: yes updated: Wed Nov 7 22:57:38 2012 (15 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: charging energy: 43.67 Wh energy-empty: 0 Wh energy-full: 625.8 Wh energy-full-design: 69 Wh energy-rate: 48.192 W voltage: 12.269 V time to full: 12.1 hours percentage: 6.97827% capacity: 97.7391% History (charge): 1352291258 6.978 charging 1352291228 6.926 charging 1352291198 6.873 charging 1352291168 6.820 charging History (rate): 1352291258 48.192 charging 1352291228 46.425 charging 1352291198 49.077 charging 1352291168 47.547 charging Despite the contradictory numbers from the kernel, and the system management chip reporting the actual level as "~60%" Expected results: Correct battery percentage is shown. Additional info: From the look of this, it would seem that this is because the energy-full-design value is out by a factor of 10 compared to the energy-full value. I assume that the percentage is calculated against this value. What would lead to this being reduced by a factor of 10 because of a suspend / resume cycle? Additionally, this reduction occurs only once. Subsequent cycles, the energy-full-design values stays only at "69Wh". Also note, that the raw values from /sys seem to be correct: # cat /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0/energy_full 67440000 # cat /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0/energy_full_design 69000000
This is still ongoing.
This is still an issue, and plays havoc with power management. It is often accompanied by messages in dmesg like upowerd[1877]: (upowerd:1877): UPower-Linux-WARNING **: energy 66.510000 bigger than full 66.230000
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This can still be produced on f18 and f19.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.