Hide Forgot
Description of problem: The X.org login manager turns off my screen. When I turn on the computer, I can see correctly my screen. But when X.org loads, the screen seems to turn off. If I change back to text console, turns on again. Go back to X.org and it turns off. If I enter through SSH and run as root: "echo 100 > /sys/class/backlight/acpi_video0/brightness" The screen turns on and I can see the login screen until the machine is suspended and the session locks. At resume, the backlight brightness is reset to 0 and I need to use SSH to reenable it. Also, if I manage to blindly enter the user password correctly with the screen off, the backlight brightness is reconfigured automatically. Version-Release number of selected component (if applicable): Fedora 20 How reproducible: Always Steps to Reproduce: 1. Turn on the computer 2. Wait until X.org loads Actual results: The screen turns off Expected results: The screen remains on Additional info: My machine is a Toshiba Satellite P75-A7200 It has two backlight controls: /sys/class/backlight/acpi_vide0 /sys/class/backlight/intel_backlight Both operates correctly the backlight brightness, but the acpi one uses a 0-100 range and Intel uses a 0-4882 range. If I copy my brighness value from acpi_video0/brighness to intel_backlight/brighness, the screen turns off because the value is to low in the Intel range. May this be the problem?
I have this problem too. Laptop is a Dell Latitude D630, (with second screen on external monitor). The external monitor does not dim/brighten, but when the laptop screen dims after not being used, it does not brighten on wakeup - I have to manually use the FN keys or run xbacklight or echo the appropriate value to the appropriate file. Unlike the original poster, I am running F19, not 20. But liek the original poster I have 2 backlight controls that both seem to affect the laptop screen: /sys/class/backlight/dell_backlight /sys/class/backlight/intel_backlight
FYI problem started when I upgraded to F 19 from F 17 - worked fine in 17 and before.
I've run this commands and the issue is partially solved: yum install lightdm systemctl disable gdm systemctl enable lightdm Now I can see the login screen, but as soon as I enter the password the backlight turns off again.
I suspect it's a common gnome component that runs both at gdm login screen and in the user session
I forgot to mention that if I turn on the computer with the AC power brick unplugged the LCD backlight turns on correctly. The issue only happens when the laptop is connected to AC power when booting.
It neither turns off if, at early boot, I change the permissions of /sys/class/backlight/intel_backlight/brightness to 0 (chmod 0 /sys/class/backlight/intel_backlight/brightness)
I booted the laptop the morning and the backlight worked correctly. I powered off and on three more times, but the backlight turned off always when running gdm. This can be a race condition.
I think I'm getting this same issue: I'm running an HP EliteBook 8460p. For me the screen is just dark and my lowest screen brightness is still visible, but responds to fn+brightness buttons. Also producible whenever I dock my computer and open/close/open the laptop screen. Screens used with the dock aren't affected.
I also have Dell D630 with the backlight issue. I read the /sys/class/backlight/intel_backlight/actual_brightness value as 255000 with a very dim screen. Performing: echo 255000 > /sys/class/backlight/intel_backlight/brightness bumped the screen back to normal brightness. I booted and ran the laptop on the AC charger for all instances of the test. Manipulating the function key brightness showed the expected screen icon, but did nothing. Same failure to change the brightness using the settings "power app". Both were restored to functionality after setting the intel_backlight/brightness to 255000 with the echo command. It sounds like a failure initialize the brightness "max" value in the driver.
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.