+++ This bug was initially created as a clone of Bug #753679 +++ 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. --- Additional comment from Kevin Kofler on 2011-11-26 09:55:32 EST --- 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). --- Additional comment from Kevin Kofler on 2011-12-12 17:33:23 EST --- This is still reproducible with 0.9.15. I just have to wait long enough and the readings will start freaking out. --- Additional comment from Giuseppe Roberti on 2012-02-07 05:39:20 EST --- 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 --- Additional comment from Fedora End Of Life on 2013-01-16 08:43:13 EST --- 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 --- Additional comment from Kevin Kofler on 2013-01-16 14:01:24 EST --- This still happens on Fedora 17. --- Additional comment from Benjamin Daines on 2013-04-01 19:02:09 EDT --- Present in F18 with upower 0.9.19-1 --- Additional comment from Benjamin Daines on 2013-04-06 22:13:40 EDT --- Present in Rawhide with upower 0.9.20
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
I'm seeing this on F20 also. Note the output below, while the laptop is unplugged and discharging (probably ~%50 at this point). It claims to have not checked the line power status for nearly 5 hours. Maybe the kernel never sent a change event? Perhaps until this works on 100% of hardware, upower can fall back to polling very occasionally? (Like once every 5 or 10 minutes or something?) Device: /org/freedesktop/UPower/devices/line_power_ADP1 native-path: /sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ADP1 power supply: yes updated: Tue Oct 22 17:31:49 2013 (17343 seconds ago) has history: no has statistics: no line-power online: yes Device: /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 Oct 22 19:53:03 2013 (8869 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: fully-charged energy: 46.238 Wh energy-empty: 0 Wh energy-full: 46.238 Wh energy-full-design: 44.5704 Wh energy-rate: 4.60891 W voltage: 8.68 V percentage: 100% capacity: 100% technology: lithium-ion Daemon: daemon-version: 0.9.20 can-suspend: yes can-hibernate: yes on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no
I started noticing this issue on F18 after a recent update about two weeks ago. The closest related package I could manage to find in yum history during the period is libgudev1 (since it was listed in upower's deplist) which was updated to 201-2.fc18.8.
Uncloning this bug. If you are seeing a different similar issue, please explain clearly how it is different, don't just clone the bug. (And a different Version is not a valid difference, this bug has been there since Fedora 16 and is still there unchanged.) *** This bug has been marked as a duplicate of bug 753679 ***