Bug 272371 - Battery widget information not getting updated
Summary: Battery widget information not getting updated
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-battery (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-03 21:58 UTC by cgc281
Modified: 2011-12-04 11:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cgc281 2011-05-03 21:58:58 UTC
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

The battery widget information (e.g., percentage, charge state, etc.) does not get updated.

Note: UPower appears to be working, as qdbusviewer shows the correct information. It seems plasma is the issue.

Reproducible: Always

Steps to Reproduce:
1. Unplug the power adapter and let the battery run down to some point.
2. Plug in the power adapter and allow the laptop to charge.

Actual Results:  
The battery widget information does not get updated (e.g., percentage does not increase, charge state remains constant, etc.).

Expected Results:  
The battery widget information should reflect UPower information (e.g., correct percentage, correct charge state information, etc.).
Comment 1 thomaslundgaard 2011-08-15 16:12:46 UTC
Hi.
I have the same issue. Both in 4.6 and after updating to 4.7.
I've also checked that the
/org/freedesktop/UPower/devices/battery_BAT0/Changed
signal is send and the
/org/freedesktop/UPower/devices/battery_BAT0/Percentage
value is correct.

I'm running archlinux, hal is not installed, upowerd installed and running.
Comment 2 Martin Klapetek 2011-12-02 16:57:00 UTC
Does the powermanagement itself works for you? Ie. does the screen goes dark after a while or the system goes to sleep when your battery is critical?
Comment 3 Aaron J. Seigo 2011-12-04 11:07:40 UTC
there is another issue open on powermanagement that has to do with upower not reporting properly anymore after a sleep or hibernate cycle. otherwise, this does seem to work accurately, so closing this report.