Bug 289696 - battery charging status is not updated
Summary: battery charging status is not updated
Status: RESOLVED DUPLICATE of bug 287952
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-battery (show other bugs)
Version: 4.7.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-23 21:18 UTC by Ettore Atalan
Modified: 2012-07-10 08:27 UTC (History)
4 users (show)

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

Attachments
2 Screenshots: Before and after reconnecting the power cord (52.39 KB, application/zip)
2011-12-23 21:18 UTC, Ettore Atalan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ettore Atalan 2011-12-23 21:18:45 UTC 
Created attachment 67069 [details]
2 Screenshots: Before and after reconnecting the power cord

Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

The battery charging status is not updated during the charging phase. It remains on the last charging status before connecting the power cord.


As workaround i used to disconnect and reconnect the power cord and the widget shows the correct charging status.

Reproducible: Always

Steps to Reproduce:
1. Discharge the battery of your mobile computer
2. Connect the power cord
3. Watch on the KDE battery monitor widget after an amount of time

Actual Results:  
The widget shows the charging status immediately before connecting the power cord.

Expected Results:  
The correct charging status of the battery at all times.
Comment 1 Diggory Hardy 2012-04-15 17:56:25 UTC 
Duplicate of #287952 or not?
Comment 2 Thijs 2012-06-22 08:34:05 UTC 
The difference between this one and bug 287952 is that this one also reports faulty behaviour without a suspend in between. But a lot has been changed in power settings since - is this still the case in 4.8.4 or newer?
Comment 3 Lukáš Tinkl 2012-07-10 08:27:10 UTC 
This has been fixed in 4.8, also for the case w/o suspend/resume

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