Bug 284597 - wrong battery status
Summary: wrong battery status
Status: RESOLVED DUPLICATE of bug 266732
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-21 08:37 UTC by jith
Modified: 2011-12-03 23:00 UTC (History)
2 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 jith 2011-10-21 08:37:16 UTC
Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

The power indicator showing wrong battery status.The percentage of the power remaining in battery not changing.for example if percentage is 69 % when charger is unplugged even if the battery became empty it shows 69 %, and not giving any warning of critical level  

Reproducible: Always

Steps to Reproduce:
unplug or plug charger and then click on battery indicator several time and close and repeat the process 

Actual Results:  
The above mentioned problems happening

Expected Results:  
It need to show status of battery uptodate and give warnings if any problems occurs
but the percentage is not changing
Comment 1 jith 2011-10-21 08:39:05 UTC
i am an regular user of kde so need to fix this bug currently i installed ubuntu 11.10
in previous versions has not this bug
Comment 2 Thijs 2011-12-03 15:47:57 UTC

*** This bug has been marked as a duplicate of bug 266732 ***
Comment 3 AE 2011-12-03 16:01:06 UTC
Dear all, please vote for bug 266732 if you want the kde developers take notice of this issue.
Comment 4 AE 2011-12-03 16:02:11 UTC
Sorry, I mean of course vote for bug 266732 which predates this one.
Comment 5 Thijs 2011-12-03 16:41:20 UTC
Andreas, what do you see when you run the acpi tool? or at least poll the situation with any other tool than the battery widget?
Comment 6 Dario Freddi 2011-12-03 23:00:52 UTC
Voting doesn't help, we notice every bug and take care of it as soon as possible. Please, continue the discussion in the open issue if any, and refrain to comment on duplicates to avoid losing possible important pieces of information. This bug is very likely upstream, as in fact mentioned in the original report.