This is somewhat bizarre. I don't know where xfce4-power-manager gets its information from, but for the last couple of days I've noticed that it is sometimes reporting things like "Adapter is online Your battery is charging (0%)", even if I've only momentarily removed the AC power supply. But acpi says: polya:~ $ acpi -i -b Battery 0: Charging, 100%, until charged Battery 0: design capacity 6600 mAh, last full capacity 5792 mAh = 87% I'm uncertain why it doesn't specify a time until charged, but it clearly says that it's 100% full, not 0%. Othertimes, though, xfce4-power-manager says 100% or another sensible percentage. I have no idea what is causing this, or where the possible bug lies. Julian
Next time it happens, please use upower to get information, since it's where xfpm gets its. Regards,
It's happening now, and this is the output of upower:
polya:~ $ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC
native-path: /sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/AC
power supply: yes
updated: Wed Sep 11 19:03:03 2013 (11987 seconds ago)
has history: no
has statistics: no
line-power
online: yes
Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0
vendor: SMP
model: DELL HP2877
serial: 26
power supply: yes
updated: Wed Sep 11 19:18:14 2013 (11076 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: fully-charged
energy: 73.26 Wh
energy-empty: 0 Wh
energy-full: 73.26 Wh
energy-full-design: 73.26 Wh
energy-rate: 1.0767 W
voltage: 12.548 V
percentage: 0%
capacity: 87.7576%
technology: lithium-ion
Daemon:
daemon-version: 0.9.21
can-suspend: yes
can-hibernate: yes
on-battery: no
on-low-battery: no
lid-is-closed: no
lid-is-present: yes
is-docked: no
So it looks like it might be upower which is "guilty" - shall I
reassign this bug report to that package?
Julian
reassign 722498 upower 0.9.21-3 retitle 722498 upower: intermittently reporting battery charge as 0% even when full thanks [Hi upower maintainer! Please see the (short) history of this bug report for more context.] Actually, it turns out that upower was updated on my system yesterday from version 0.9.21-2 to -3, so it looks like that's the source of the problem. Reassigning. Julian