Bug 284597

Summary:	wrong battery status
Product:	[Frameworks and Libraries] solid	Reporter:	jith <jithinkumarkp>
Component:	powermanagement	Assignee:	Dario Freddi <drf>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aspotashev, thijs22nospam
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

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.