I currently use a laptop in a docking station with an external monitor as the only active display. Before undocking I use xfce4-display-settings to enable the laptop display. However simply checking the "Use this output" checkbox does not activate the laptop display. If I change the resolution, rotation or reflection the laptop monitor activates with the new settings but I must use "Restore the Previous Configuration" button on the subsequent dialog. Unselecting the checkbox immediately disables the laptop display. xfce4-display-settings 4.8.3 (Xfce 4.8) X.Org X Server 1.11.4 How reproducible: Boot system with laptop docked and only external monitor active. Run Applications Menu->Settings->Display Select Laptop monitor then select "Use this output" Observe laptop monitor does not activate Additional info: The output from "xrandr --verbose" is identical for the case where the checkbox is selected but the screen off, and the case where both monitors are active. This is printed to Xorg.0.log when selecting the checkbox [ 87898.618] (II) intel(0): EDID vendor "AUO", prod id 9079 [ 87898.619] (II) intel(0): Printing DDC gathered Modelines: [ 87898.619] (II) intel(0): Modeline "1440x900"x0.0 108.00 1440 1504 1536 1970 900 903 906 912 +hsync -vsync (54.8 kHz)
Thanks for the report. Will try and track it down.
I've filed this upstream as: https://bugzilla.xfce.org/show_bug.cgi?id=8529
For the record: I am using external displays quite frequently (I also have a laptop and a docking station) and I cannot reproduce the problem.
As of today, I still see this behavior. I did some more testing however. After booting while docked, the login is displayed on the laptop screen. After logging in, the external monitor is automatically activated and the laptop monitor deactivated. If I then run Settings->Display and uncheck HDMI1, I get a helpful error message indicating I would have no active monitors. If I then enable the laptop monitor, it does not activate as described above. Display now shows both monitors with 'Use this output' checked but only the external monitor is active. Now if I uncheck HDMI1, I get no error message and BOTH monitors are deactivated. Pressing spacebar to check the box brings back the external monitor. One final effect I see. When I tell display to activate the laptop monitor, a duplicate wallpaper the same dimensions as my laptop display is overlaid on the external monitor. It almost seems like the laptop 'drawing area' is activating but is being placed directly over the HDMI1 screen.
This still exists after upgrading to F17.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17'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 Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.