Description of problem: I have a Thinkpad T520 running latest F20 x86_64. I usually connect to a Dell Ultrasharp LCD monitor via the Thinkpad's HDMI port using a HDMI-DVI adapter. When I disconnect the adapter the laptop screen resets brightness to a very low value and the screen background goes black I have to manually change the desktop background back to original settings every time this happens Version-Release number of selected component (if applicable): F20 latest updates as of Jan 8 2014 How reproducible: See Desc Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
gnome-shell-3.10.2.1-3.fc20.x86_64 xorg-x11-drv-intel-2.21.15-5.fc20.x86_64
I'm running a F20 x86_64 on a dell latitude e6400 (Intel Corporation Mobile 4 Series Chipset) and I experience something similar when I disconnect my external Dell LCD (connected via HDMI). The background turns white and I have to go into the control panel to re-select the wallpaper to fix it. I don't notice anything with the brightness though.
Correction, my external monitor is connected via DisplayPort, not HDMI
Was able to duplicate when connected via VGA as well as DP.
When external monitor is set as Secondary in Monitors control panel I don't experience this behavior. Only when the external display is set as the Primary and then disconnected do I witness this bug.
(In reply to patrick korsnick from comment #5) > When external monitor is set as Secondary in Monitors control panel I don't > experience this behavior. Only when the external display is set as the > Primary and then disconnected do I witness this bug. I have a Thinkpad T420 and have the same issue.
I have a Lenovo X1 Carbon and experience the brightness issue (but not the background problems). Same as patrick, if my laptop display is set as the primary monitor then I retain brightness control after disconnecting the external monitor. My external monitor is connected via DP. I will test with DVI and see if the problem still occurs.
I ran into the background changing bug some time ago but I think it is fixed in 3.12 (from COPR running on F20). As for the brightness bug: this (or a variant) has been driving me crazy for month. It started with my internal laptop screen showing a black screen and the external showing gray. I soon realized I could log in "blind" anyway. Finally I enabled autologin to work around this. What I realize now: the internal screen was never "black" but 0% brightness. From some angle you can still barely see what's going on. The problem is: using latest updates (F20 + COPR gnome 3.12) the autologin workaround does not work anymore because it now happens inside the session, too. The problem does not occur when the external screen is not connected. It is connected using mini-displayport. Using intel graphics.
Btw in my case I do not even disconnect any screen. With just the internal screen everything is fine, as soon as I connect the external screen (or boot with it connected) the brightness bug is triggered.
Getting the same issue with Thinkpad T430s with the most recently updated gnome-shell version: gnome-shell-3.10.4-4.fc20.x86_64. Running dual monitor setup through the Thinkpad dock, with both a VGA and DVI connector. Anytime I change to or from dock backgrounds go to black and brightness is set to lowest value. Seems to be easily replicated across multiple hardware types and configurations (seen by various colleagues). Reported in January, we are in June, any chance for an ack or response?
(In reply to BJ Walker from comment #10) > Getting the same issue with Thinkpad T430s [...] I reported my problem upstream¹. [1] https://bugs.freedesktop.org/show_bug.cgi?id=79581
I'd like to confirm the same issue on T420s hardware running gnome-shell-3.10.4-2.fc20.x86_64. I can replicate the same as @BJ in comment #10
Same here on a Thinkpad T520: gnome-shell-3.10.4-5.fc20.x86_64 gnome-settings-daemon-3.10.2-3.fc20.x86_64
Same problem here with screen brightness on the external display (VGA). System is Lenovo X230. gnome-shell-3.10.4-9.fc20.x86_64 gnome-settings-daemon-3.10.3-2.fc20.x86_64
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.