Bug 301601 - Solid doesn't know anything about battery
Summary: Solid doesn't know anything about battery
Status: RESOLVED DUPLICATE of bug 301033
Alias: None
Product: solid
Classification: Unmaintained
Component: libsolid-upower (show other bugs)
Version: 4.8.80 (beta1)
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-10 21:13 UTC by Evgeny Brazgin
Modified: 2012-06-11 10:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Evgeny Brazgin 2012-06-10 21:13:40 UTC
Battery applet in plasma says, that there's no battery present in my system.

When I open 'kcmshell4 devinfo' and open "Batteries - 42T4861", I see in the right side: "Battery type: unknown. Charge state: nothing" (or something like this, I have russian localization).

In the bottom I see: "UDI: /org/freedesktop/UPower/devices/battery_BAT0". So I check whether upower is aware of my battery.
See the output of upower here: http://paste.kde.org/496874/

So, the problem is neither in my battery nor in upower. But in solid or solid's upower backend.

Restarting computer doesn't help.

Reproducible: Always

Steps to Reproduce:
Look at battery applet.
Actual Results:  
See 'no battery present'

Expected Results:  
Want to see battery state.
Comment 1 Evgeny Brazgin 2012-06-10 21:35:09 UTC
Some addition:

$ solid-hardware details /org/freedesktop/UPower/devices/battery_BAT0
udi = '/org/freedesktop/UPower/devices/battery_BAT0'
  parent = '/org/freedesktop/UPower'  (string)
  vendor = 'SANYO'  (string)
  product = '42T4861'  (string)
  description = 'Lithium Ion Battery'  (string)
  Battery.plugged = true  (bool)
  Battery.type = 'UnknownBattery'  (0x0)  (enum)
  Battery.chargePercent = 59  (0x3b)  (int)
  Battery.rechargeable = true  (bool)
  Battery.chargeState = 'Discharging'  (0x2)  (enum)


Here I am able to see charge percent.
Comment 2 Christoph Feck 2012-06-11 10:32:22 UTC

*** This bug has been marked as a duplicate of bug 301033 ***