http://bugzilla.novell.com/show_bug.cgi?id=623254 http://bugzilla.novell.com/show_bug.cgi?id=623254#c6 --- Comment #6 from Reinhard Max <max@novell.com> 2010-07-21 10:59:59 CEST --- Keith, the bug I fixed was in the generic X server code, so it can be reproduced with the unpatched versions of all kinds of X servers that are built from the xorg-x11-server source package (e.g. /usr/bin/Xorg, /usr/bin/Xnest, and /usr/bin/Xvnc). To check that the gdm issue you are seeing is really a separate one, please make sure that you have the patched version of Xnest. For the patched version, it should look like this: --- snip --- $ rpm -qf /usr/bin/Xnest --changelog | head -9 * Do Jul 08 2010 max@suse.de - Fix some shortcomings in the xdmcp implementation. It used to suppress loopback addresses from the list of potential display addresses to report to xdm, even when talking to xdm through a loopback address. Now only display addresses of the same kind as the xdm connection are reported to xdm. This most notably helps Xvnc servers contacting the local xdm, because they were severely affected by the suppression of loopback addresses. --- snap --- Ah - I just see you are connecting to a remote xdm (or gdm), not a local one, so it is outside the scope of my fix. In that case, please check if that problem was actually caused by my fix, i.e. if the Xnest problem disappears when you downgrade the xorg-x11-server-extra package to the stock 11.3 version. BTW, the IPv6 address gdm prints out in the logs you pasted looks a bit strange to me: ::ec51:86b7:2fff:82b7 . What kind of address is this supposed to be? It looks neither like an IPv4 mapped address nor like a link local or global address. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.