Description of problem: Selecting Dual Head in System -> Administration -> Display -> Display Settings crashes X11. This happens both in Fedora 8-i386 as well as in Fedora 8-64. Switching back to the original xorg.conf configuration file restores proper operation of X11. System consists of: Intel Core2 Quad 6600; Asus P5K mobo: nVidea GeForce 8600 GTS display; One Hitachi Super Scan 753 and One NEC AccuSync LCD 193 wxm monitors; 2 GB memory: 2 x 400 GB Sata Drives. Attached the F8-64 xorg,conf which causes the crash and the Xorg.0.log. Version-Release number of selected component (if applicable): X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Fedora Core 7 Red Hat, Inc. Current Operating System: Linux dhcppc1 2.6.23.1-49.fc8 #1 SMP Thu Nov 8 22:14:09 EST 2007 x86_64 Build Date: 17 October 2007 Build ID: xorg-x11-server 1.3.0.0-33.fc8 How reproducible: Consistent Steps to Reproduce: 1.System -> Administration -> Display -> Display Settings -> Dual head 2.Select use dual head, configure second monitor (Generic 1440x900) 3. Actual results: Crash Expected results: Additional info:
Created attachment 271871 [details] Xorg Crash support files
Created attachment 273081 [details] xorg.conf which doesn't work
Created attachment 273091 [details] xorg.conf which does work
Created attachment 273101 [details] Screenshot of system-config-display with the current configuration
Created attachment 273111 [details] Xorg.0.log not clear which configuration it is
Created attachment 273121 [details] Xorg.0.log not clear which configuration it is
Comment on attachment 273121 [details] Xorg.0.log attaached twice by mistake
Does X crash immediately upon configuring the second monitor, or only after restarting X? If the latter, can you attach the X log from the crash? (Reboot into runlevel 3 and copy /var/log/Xorg.0.log away to somewhere safe, then telinit 5.)
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
With recent updates the problem has vanished. You may close this bug. Thank you. M. A. MacLain