Bug 310723 - Battery status not upated
Summary: Battery status not upated
Status: RESOLVED DUPLICATE of bug 301033
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-battery (show other bugs)
Version: 4.9.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-26 17:48 UTC by Detlev Casanova
Modified: 2012-12-27 09:22 UTC (History)
1 user (show)

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 Detlev Casanova 2012-11-26 17:48:59 UTC
When I Remove the battery from the laptop, the proper icon shows that tthere is no battery but when I put it back, nothing happens.
The widget's popup still says "Battery : Not present" but the battery is there.
If I remove the cable, It says no no battery and no AC adapter, which is quite weird.

Each time I remove the battery, plasma-desktop says :

file:///usr/share/apps/plasma/plasmoids/battery/contents/ui/batterymonitor.qml:175: TypeError: Result of expression 'pmSource.data["Battery0"]' [undefined] is not an object.
file:///usr/share/apps/plasma/plasmoids/battery/contents/ui/batterymonitor.qml:174: TypeError: Result of expression 'pmSource.data["Battery0"]' [undefined] is not an object.
file:///usr/share/apps/plasma/plasmoids/battery/contents/ui/batterymonitor.qml:53: TypeError: Result of expression 'pmSource.data["Battery0"]' [undefined] is not an object.
file:///usr/share/apps/plasma/plasmoids/battery/contents/ui/batterymonitor.qml:52: TypeError: Result of expression 'pmSource.data["Battery0"]' [undefined] is not an object.

I'm not a qml expert so I don't really understand what's happening (There are no messages when I plug it back in).

upower properly detect the plugging and unplugging.
Comment 1 Bogdan Mihaila 2012-12-27 09:12:28 UTC
Should be a duplicate of https://bugs.kde.org/show_bug.cgi?id=301033
Comment 2 Jekyll Wu 2012-12-27 09:22:32 UTC

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