User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 After updating the kernel to 3.3.0-8 version, the kde battery monitor reports two batteries instead of the one that really exists, meaning another one in addition to the real battery. The charge level of the real battery is correct as well as whether the laptop is connected to AC or not or charging, but the second fake battery is always reported as discharging. If I go back to the 3.2 kernel, battery info is correctly reported. Reproducible: Always Running Fedora 16 KDE Spin with KDE 4.8.1.
The kernel was what was upgraded when the bug sprang up, so I'd blame the kernel first of all. Plasma can only report what upower reports, and upower can only report what the kernel reports.
Output of: udisks --enumerate (ideally before and after up'ing kernel to 3.3) may help give a clue
I think Rex meant upower --enumerate
The kernel was not the only component upgraded at the time, however if I change back to a previous kernel like 3.2.10 (which I have installed alongside the 3.3.0 kernel), then the issue doesn't happen, only in 3.3.0. The following is the output of upower --enumerate in kernel 3.2.10 $ upower --enumerate /org/freedesktop/UPower/devices/line_power_ACAD /org/freedesktop/UPower/devices/battery_BAT0 and kernel 3.3.0 $ upower --enumerate /org/freedesktop/UPower/devices/line_power_ACAD /org/freedesktop/UPower/devices/battery_BAT0 /org/freedesktop/UPower/devices/battery_hid_00o02o76o23o15o78_battery.
ok, next when in 3.3.0, upower --show-info \ /org/freedesktop/UPower/devices/battery_hid_00o02o76o23o15o78_battery
Output of: $ upower --show-info \ /org/freedesktop/UPower/devices/battery_hid_00o02o76o23o15o78_battery native-path: /sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2:1.0/bluetooth/hci0/hci0:11/0005:1048:03ED.0001/power_supply/hid-00:02:76:23:15:78-battery model: Targus Soft-Touch Bluetooth Mouse power supply: yes updated: Wed Apr 4 02:11:22 2012 (30 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: discharging energy: 0 Wh energy-empty: 0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 17% capacity: 100% History (charge): 1333501848 17.000 discharging 1333501848 0.000 unknown History (rate): 1333501848 0.000 unknown Surprise (at least to me)! It's referring to the batteries of my bluetooth mouse. Interestingly, Windows 7 is capable of detecting the battery level of my bluetooth mouse. Nonetheless, it is a separate figure from the battery level of the battery of the laptop. If it's a new feature of KDE 4.8, I'm pleased to see that KDE is now capable of reporting this, but still it would be better to report it separately somehow. Right now it is treated as one more battery in the computer by the kde battery monitor.
With this new piece of information, I think this bug is surely related if not duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=806295.
Yes, it's the same bug. *** This bug has been marked as a duplicate of bug 806295 ***