From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Description of problem:
When browsing for XDMCP X servers to connect to via the F10 button in
GDM returns 0 servers. If you add a server manually it's kernel
version and user load are correctly identified but when you connect
the X server goes black - you left with the X cursor but nothing else.
I think this might be SE-related... there are some SE-type messages in
the syslog but I don't understand them!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. load with init 5 with gdm as the login manager (default)
2. Hit F10, choose XDMCP browser
--- the browser will return 0 results
3. Manually add a host and click on "Connect"
4. Watch the awesome black screen-saver.
Actual Results: No results in browser
Expected Results: A big list of all our XDMCP-enabled Linux servers
Can you attach the SELinux messages?
I don't know that this IS selinux related now. It still fails to run
when I echo 0 > /selinux/enforce.
I get a similar problem.
I have installed RedHat Linux ESS 3. When I try to connect to the RH
server using Exceed (or XWin32), it does not show the server. There
is no firewall problem as the RH server and the Windows PC I am
trying to connect from are on same subnet.
I think XDM requests are blocked by default. Could you let me know
what is the procedure to enable XDM request response.
Sameer, this is probably not related and sounds more like a firewall
problem (does it work with the firewall disabled?).
Havoc - is there anything I can do to help you with this bug?
Steve, There are no firewall issues as they are logically on the same
subnet and all ports are allowed between these the RH server and Win
PC. The WinPC can connect to Sun and IBM servers, but hangs on trying
to access RH server.
I believe that the XDMCP might be disabled by default on RH ESS 3
server. I need to know how to enable this. I tried modifying the kdmr
file, but still does not work.
I'm going through bugs assigned to me and attempting to clean some of the older,
fixed ones up.
This bug hasn't changed in over a year old now. Are you still seeing the problem?
(This a batch message is being sent to all my bugs that haven't changed in a year)
This bug has been in the NEEDINFO state for at least a couple of weeks now. I'm
going to close the bug, but if you can provide the required information feel
free to open a new report.
(This is a mass message being sent to a bunch of bug reports)