Bug 285744 - Battery monitor wrong info. Power management randomly changing my display settings.
Summary: Battery monitor wrong info. Power management randomly changing my display set...
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: solid
Classification: Unmaintained
Component: powermanagement (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-04 11:32 UTC by Diego Ocampo
Modified: 2013-04-25 16:15 UTC (History)
3 users (show)

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


Attachments
shows the battery monitor (154.42 KB, image/jpeg)
2011-11-04 11:32 UTC, Diego Ocampo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Ocampo 2011-11-04 11:32:32 UTC
Created attachment 65227 [details]
shows the battery monitor

Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

If I use my laptop without plugin it in the battery monitor applet shows the right information. I plug it in, the screen resolution changes from 1366x768 to 1024x768 and the battery monitor icon doesn't change and gives the following information: battery xx% (charging), AC adapter: Not plugged in (which is of course wrong).

Since I plug it in I get random display resolution changes each 5-10 minutes until it finally doesn't do that anymore. I attach picture with the battery monitor showing the wrong information (how can it be charging if it is not plugged in???)

Reproducible: Always

Steps to Reproduce:
It's been explained in Details section

Actual Results:  
It's been explained in Details section

Expected Results:  
It's been explained in Details section
Comment 1 Oliver Henshaw 2013-02-27 17:51:15 UTC
Is this still a problem? Is it a problem with 4.9 or 4.10?

If so, do you use the Hal backend  or the upower backend?
Comment 2 Alex Fiestas 2013-04-25 16:15:30 UTC
Closing the bug for lack of info.

Please, if you can still reproduce with 4.10 feel free to reopen the bug.

Thanks !