Hide Forgot
Description of problem: The gamma value can be changed using kgamma but cannot be loaded automatically on reboot. On reboot the changed value is not loaded automatically.A high default value is loaded. So brightness of the LED display is beyond tolerance. so forcing to open 'kgamma setting'(on opening kgamma setting the saved required value is loaded automatically with out adjusting the gamma slider) after each and every reboot. Version-Release number of selected component (if applicable): How reproducible: changed kgamma value to required low value(say 50) and reboot. Steps to Reproduce: 1.changed kgamma value 2.reboot 3.open 'kgamma setting'(on opening kgamma setting the saved required value is loaded automatically with out adjusting the gamma slider) Actual results: changed gamma value not loaded automatically. forcing to open 'kgamma setting' on each and every reboot. Expected results: Load changed gamma value(user specific) automatically on reboot. login screen can use the gamma setting of root or a separate value. more controls(hue, contrast, etc) are appreciated Additional info: Uses radeon HD 4000 series(HD4290)IGP . bug 696621 does not mention kgamma.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.