There is a bug in the patch applied as a result of bug 295600. Whenever the Battery plasmoid is clicked the screen brightness is set down to 0 and the slider defaults to the lowest position regardless of active profile or default brightness. The screensaver also seems to trigger this behavior (or the system does not properly restore brightness after dimming for the screensaver) as do potentially other things (it may happen randomly with time, not sure). I attached gdb to plasma-desktop and stepped through execution and found that execution never branches into halpower.cpp:388 leading me to believe deviceList is not populated correctly anymore and the changes in revision 1035622 were what actually caused the bug. If I get time I will verify (currently in the midst of univ. exams so if someone else could verify it will probably be quicker). Obviously this will need to be reported upstream for the final fix.
Reported upstream: https://bugs.kde.org/show_bug.cgi?id=196232 Pending svn commit for a new patch for solid-4.3.4-r2
I was too frustrated by this to wait to finish my exams so I went ahead and too the time to squash it. Attached is the new ebuild, modified original patch, and the new patch which together fix two bugs. I will report this upstream so they know to investigate. Thanks ---Nate
Created attachment 212849 [details] Ebuild Forgot to mention, I tested this against hal-0.5.13-r2 and 0.5.14 (most recent in portage tree which bought this bug up).
Created attachment 212851 [details, diff] Corrected previous patch
Created attachment 212852 [details, diff] New powermanager patch
Tested with hal-0.14, Qt-4.6. Works fine. Many thanks for taking this up!
Patched upstream per bugs: http://bugs.kde.org/show_bug.cgi?id=217316 http://bugs.kde.org/show_bug.cgi?id=196232
*** Bug 297166 has been marked as a duplicate of this bug. ***
+*solid-4.3.4-r2 (16 Dec 2009) + + 16 Dec 2009; Samuli Suominen <ssuominen@gentoo.org> + -solid-4.3.4-r1.ebuild, +solid-4.3.4-r2.ebuild, + files/solid-4.3.4-hal.patch: + Update HAL 0.5.14 patch wrt #296544 by Nate Weibley.
This patch resolve issue (for me) only in the way that setting brightness stop work too. I must open new bug or reopen this?