Description of problem: When unplugging the power cord on a laptop the applet switches to Powersave, and dims the monitor. It further dims the monitor when going to aggressive powersave. However, when the cord is plugged back in it goes to Performance, but the screen brightness stays the same, dimmed. When I noticed this I tested by unplugging the power cord again, and it went to powersave, while remaining at full brightness. (I had manually set the brightness back to high). Version-Release number of selected component (if applicable): KDE Plasma applet battery monitor 4.6.3 How reproducible: I haven't tried after a logout or reboot, but now it seems to be a consistent problem. Steps to Reproduce: 1.Unplug the power cord. 2.Plug it back in.
Source RPM: plasma-applet-battery-4.6.3-7.mga1.src.rpm => kdebase4-workspace-4.6.3-7.mga1.src.rpm
CC: (none) => magnus.mud
I've got the same problem, but the first thing I see, when looking into it now, is that the only energy profile I seem to have is "Prestatie" ("Prestation") I don't have time to look any further now.
CC: (none) => marja11
Hardware: i586 => All
(In reply to comment #1) > I've got the same problem, but the first thing I see, when looking into it now, > is that the only energy profile I seem to have is "Prestatie" ("Prestation") > > I don't have time to look any further now. that is another bug, 1874, and the only profile I had there is called "Performance" in English. Because I don't have the three default energy profiles, I can't exactly reproduce this problem. But I did add a powersave profile and did set it to be activated when the power cord is unplugged, and I did set the Performance profile to be activated when the power cord is plugged back in. The first thing: the screen dimming when unplugging the power cord, works. And the second, the screen getting bright again when plugging in the cord, doesn't, exactly as happened with you. Only when I set brightness to full again and unplug again, for me it gets dimmed as it should, so that part of the issue I can't reproduce. Assigning to maintainer
Assignee: bugsquad => balcaen.john
It should be reported upstream (probably against solid )with information regarding the laptop you're using. I've got only one netbook here (Asus EeePC1001PX) & it's working correctly.
CC: (none) => balcaen.john
(In reply to comment #3) > It should be reported upstream (probably against solid )with information > regarding the laptop you're using. > I've got only one netbook here (Asus EeePC1001PX) & it's working correctly. Thx, I wouldn't ever have guessed "solid" should be chosen, hadn't you said so. Which solid component should it be? https://bugs.kde.org/describecomponents.cgi?product=solid @ Max none: I think it is better you report upstream than me, because your problem is more severe than mine and besides, I use this laptop as a desktop so I don't use the battery - except to reproduce a bug ;) Apart from that I don't know which laptop you've got. You can report here: http://bugs.kde.org/ and can add that I confirmed most of the bug on a ThinkPad SL510 and link to the report here. Please put a link to the upstream report in the URL: field of this bug report.
Keywords: (none) => UPSTREAM
URL: (none) => https://bugs.kde.org/show_bug.cgi?id=286688
@ Max Do you have time to check what Anne-Marie Mahfouf said in your upstream bug report and to confirm or not?
(In reply to comment #5) > @ Max > > Do you have time to check what Anne-Marie Mahfouf said in your upstream bug > report and to confirm or not? That is precisely the behavior I am seeing in KDE 4.6
URL: https://bugs.kde.org/show_bug.cgi?id=286688 => (none)See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=286688
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Setting this as RESOLVED OLD since in Mga 2 KDE 4.8 this seems to have been fixed.
Status: NEW => RESOLVEDResolution: (none) => OLD