Description of problem: The 'Display' settings in gnome-control-center leave my external display flickering and unusable when I click 'Apply' twice. Version-Release number of selected component (if applicable): control-center-2.91.92-1.fc15.i686 How reproducible: always Steps to Reproduce: 1. Boot my Thinkpad X201 (1280x100) with external 24" Samsung 2494 HM (1920x1080) attached. 2. Gnome-shell starts and automatically expands the desktop to the secondary display. 3. Start control-center -> 'Display' a. Don't change anything and just click 'Apply' OR b. Change something and hit 'Apply'. Changes are applied, everything is fine as long as I don't click 'Apply' again without making changes before. Actual results: The external display flickers red, no way to get return to the previous settings and it' not returning to the previous settings after the timeout because nothing was changed. Expected results: Nothing should happen if 'Apply' is clicked twice, in fact the button should be greyed out. Additional info: The settings that make the external display unusable are restored after reboot. There is no way to get working settings back if the external display was marked primary. This can lead to data-loss and therefore I'm marking this bug high severity.
I experienced this morning when I tried to switch the "primary" display by dragging the black bar from the laptop display to the external VGA display. (This was completely non-intuitive by-the-way; I had to do a few Google searches to learn that you could drag the little black bar.) Using the command line worked fine, though: xrandr --output VGA1 --primary xrandr --output LVDS1 --primary I toggled the primary display back-and-forth many times and the system was stable. It was only when I tried the control-center and dragged the black bar that the external display just started blinking red and I had to reboot. I have a Lenovo T510 with an Intel graphics chip. 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This was actually fixed in F16 / GNOME 3.2.
*** Bug 892183 has been marked as a duplicate of this bug. ***