Description of problem: After fresh install on my netbook i updated all packages. Screen brightness was working with latest stable kernel. After a few minutes on idle KDE tries to dimm the screen. This resultet in heavy screen flickering ( a common problem in most distributions on this type of netbook). But after a reboot i was no longer able to set the brightness any more. Even installing the netbook-kernel diddnt resolve the problem. output lsmod: http://pastebin.com/gYdZyyim Version-Release number of selected component (if applicable): How reproducible: Install latest Mageia 1 on the N220. Wait for KDE to lower brightness. Then restart and try to use fn-keys or KDE Powermangement to adjust brightness. Steps to Reproduce: 1. 2. 3.
same as bug 2175 ?
(In reply to comment #1) > same as bug 2175 ? Not really. As i said before the brightness setting with fn keys is working with latest stable kernel (You can adjust only it three steps but hey thats enough for me). But sometimes (like in suse or now in mageia) the module seems to get out of control (screen flickering and the applet for brightness setting goes up and down itself). For example see this Ubuntu Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810093 It seems to me that something in the module is crashing and after reboot it stays corrupted so the brightness control isn't working like befor the crash. Installing other stable kernels does not resolve the problem.
Assignee: bugsquad => tmb
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Thomas Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
3-monthly ping
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
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
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX