Description of problem: X session conflict Version-Release number of selected component (if applicable): How reproducible: same occurs on two systems Steps to Reproduce: 1. Allow XDCMP connections to a machine running KDE session 2. Let the GDM greeter handle opening sessions 3. Connect through XDMCP from a remote computer, run KDE session 4. Close the remote session, e.g. log off Actual results: The KDE on a host machine breaks down immediately, a blue screen comes, informing of an attempt to use screen :0 from another machine and the resulting conflict. Similar happens when an external thin client runs an X session remotely through an "X -query <host>" command, and then disconnects. Expected results: In FC3 and all the previous versions, session on host was not interrupted in similar circumstances Additional info:
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 144445 [details] original xorg.conf file
Created attachment 144446 [details] original log file (before X autoconfiguration)
Created attachment 144447 [details] original log file (before X autoconfiguration)
Created attachment 144448 [details] original log file (before X autoconfiguration)
Created attachment 144449 [details] original log file (before X autoconfiguration)
Created attachment 144450 [details] original log file (before X autoconfiguration)
Created attachment 144451 [details] original log file (before X autoconfiguration)
Created attachment 144452 [details] original log file (before X autoconfiguration)
Created attachment 144453 [details] original log file (before X autoconfiguration)
Created attachment 144454 [details] original log file (before X autoconfiguration)
Created attachment 144455 [details] xorg.conf file after automatic configuration
Created attachment 144456 [details] log file after X autoconfiguration and closing a remote KDE session
Note that this problem is apparently not hardware-specific - I observed it on three machines: the one with nVidia (logs attached), on a Tyan Transport equipped with an onboard ATI, and on a laptop with Intel video chip
*** Bug 220591 has been marked as a duplicate of this bug. ***
Fedora Core 5 is no longer supported, please, could you reproduce this bug with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX/INSUFFICIENT_DATA. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance.
This problem disappeared in Fedora 7.