Description of problem: On my Notebook (AsMobile S37E), upower is reporting that the battery is "fully charged", but a percentage very very far from 100%: [kevin@laptop64 ~]$ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0 vendor: Intel model: S37E power supply: yes updated: Mon Nov 14 04:12:45 2011 (4307 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: fully-charged energy: 53.0025 Wh energy-empty: 0 Wh energy-full: 476.401 Wh energy-full-design: 55.5 Wh energy-rate: 100.566 W voltage: 12.373 V percentage: 11.1256% capacity: 95.5% technology: lithium-ion A reboot makes the issue go away for a while, then it eventually comes back. I've never seen that nonsense in Fedora 15, the trouble started after upgrading to Fedora 16. Version-Release number of selected component (if applicable): upower-0.9.14-1.fc16.x86_64 How reproducible: Not sure. I had it happen twice now, and it looks like waiting long enough after a reboot will always make it show up on my hardware, but I don't have sufficient evidence to confirm this. Steps to Reproduce: 1. Boot the notebook. 2. Log into KDE Plasma. 3. Wait for a while, until the battery plasmoid starts displaying a nonsensical percentage. 4. Check upower -i /org/freedesktop/UPower/devices/battery_BAT0 Actual results: energy-full: 476.401 Wh percentage: 11.1256% Expected results: energy-full: 53.0025 Wh percentage: 100% Additional info: Originally reported in https://bugzilla.redhat.com/show_bug.cgi?id=753429#c4 but I suspect it's actually not the same issue.
Ping? This issue is still present with the current updates, and it's not the same as bug #753429 (which was a kdebase-workspace issue and is already fixed, but this one is in upower, the upower command line reports the same wrong readings).
This is still reproducible with 0.9.15. I just have to wait long enough and the readings will start freaking out.
Hi, i also have this BUG on Samsung 700Z5A S01 # cat /etc/fedora-release Fedora release 16 (Verne) # upower --version UPower client version 0.9.15 UPower daemon version 0.9.15 # upower -i /org/freedesktop/UPower/devices/battery_BAT1 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/PNP0C09:00/PNP0C0A:00/power_supply/BAT1 vendor: SAMSUNG Electronics power supply: yes updated: Tue Feb 7 10:53:05 2012 (2665 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: fully-charged energy: 78.44 Wh energy-empty: 0 Wh energy-full: 200.022 Wh energy-full-design: 80.216 Wh energy-rate: 55.6332 W voltage: 16.569 V percentage: 39.2157% capacity: 97.786% technology: lithium-ion
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This still happens on Fedora 17.
Present in F18 with upower 0.9.19-1
Present in Rawhide with upower 0.9.20
I'm experiencing the same thing on Fedora 18 on my Asus Zenbook UX21A. The symptom is the following: After running for more than a couple of hours on AC (the laptop is plugged in for the whole time), upower says that the battery charge percentage is 57%, even though it's in fact full. A reboot or a suspend/resume will make the problem go away for a while and then the same thing happens. Here's the output of 'upower -e' /org/freedesktop/UPower/devices/line_power_AC0 /org/freedesktop/UPower/devices/battery_BAT0 And the output of 'upower -i /org/freedesktop/UPower/devices/battery_BAT0' native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0 vendor: LIon serial: UX21-48 power supply: yes updated: Tue Jun 25 11:44:09 2013 (11 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: charging energy: 35.542 Wh energy-empty: 0 Wh energy-full: 61.856 Wh energy-full-design: 0 Wh energy-rate: 1.42 W voltage: 7.4 V time to full: 18.5 hours percentage: 57.4593% capacity: 100% Out of curiosity, I also looked around in the place which upower reports as the "native-path". 'cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0/energy_now' says 35542000 'cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0/energy_full' says 35520000 After this, I put the laptop to sleep and then woke it up. Now the two above files in /sys still say the same but upower changed its mind. upower -i tells this: native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0 vendor: LIon serial: UX21-48 power supply: yes updated: Tue Jun 25 11:45:27 2013 (10 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: fully-charged energy: 35.542 Wh energy-empty: 0 Wh energy-full: 35.542 Wh energy-full-design: 0 Wh energy-rate: 0 W voltage: 7.4 V percentage: 100% capacity: 100% History (charge): 1372153522 100.000 fully-charged 1372153522 0.000 unknown History (rate): 1372153522 0.000 unknown
I'm also still seeing this on F18. This is now the third broken release, and judging from comment #7, it looks a lot like F19 will be the 4th. :-(
(In reply to Timur Kristóf from comment #8) > A reboot or a suspend/resume will make the problem go away for a while and > then the same thing happens. Given this seems to span several ACPI kernel versions, I'm thinking this is probably a firmware bug. Can you all confirm there are no firmware updates and if there are, try the new releases? This looks very odd: energy-full-design=0, energy-rate=0 and either the battery is broken (well, the embedded microcontroller) of the firmware is crazy. There's not much upower can do in these cases.
In my case, energy-full-design is not 0, it's in fact correct, so I think the bug from comment #8 is a different bug and should be filed separately. (But my bug is also still there! And I'm running the last BIOS update that was issued for my notebook. Updating the BIOS was the first thing I did when I got the notebook, even before installing Fedora 9. There have been no BIOS updates since.)
Bumping Version, this is still not fixed in fully updated F19.
*** Bug 949204 has been marked as a duplicate of this bug. ***
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.