Description of problem: While running Xorg, if a new instance of X is started using X :1 or X :1 -query <IP> the second instance works fine but when one switch back to the original instance using CTRL + ALT + F7, the screen either goes blank or its garbled. The system is responsive and doesn't hang. Attempting to get a shell in the other VTs is not possible as CTRL + ALT + F1 .. F6 lead to empty / garbled screens. Pressing the poweroff button and allowing the machine to switch itself off and restarting it is the only option Version-Release number of selected component (if applicable): Not sure which component is the culprit. How reproducible: Always Steps to Reproduce: 1. Boot F9 2. Login to GNOME 3. Open a console 4. run X :1 -query <another machine's IP> 5. Try switching back using CTRL + ALT + F7 Actual results: Display is garbled / non existent. Expected results: The display should continue working normally i.e. the two sessions on VT7 and VT9 should continue executing parallely. Additional info: 1. SELinux is disabled completely. 2. Machine is a Dell 510m laptop. 3. Earlier versions of Fedora didn't exhibit this behavior.
Created attachment 307696 [details] lspci output
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 308454 [details] original xorg.conf
Created attachment 308455 [details] this is the original Xorg.0.log file ( BEFORE I ran Xorg without a .conf file )
Created attachment 308456 [details] Xorg.2.log
Created attachment 308457 [details] Xorg.1.log
Created attachment 308458 [details] Xorg.3.log
Created attachment 308459 [details] Xorg.4.log
Created attachment 308460 [details] Xorg.5.log
Created attachment 308462 [details] This is the Xorg.0.log file that was generated AFTER I removed the xorg.conf file
I've added attachments for whatever you had asked for.
Maybe related to bug 238974?
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.