Red Hat Bugzilla – Bug 171490
Cannot get gnome-desktop after entering username/password via XDMCP broadcast
Last modified: 2007-11-30 17:07:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Not esay! It depends on a number of Exceed users on server
When we log into the linux server with Exceed over XDMCP broadcast and enter
username/password, we don't get GNOME desktop but just blank screen forever
until we execute "service xinetd restart" on the linux server or restart gdm.
We don't have a problem for first 14 ~ 16 days every time we restart a linux
server, but after this period, we must restart xinetd every hour otherwise
noone can use GNOME desktop. It is very annoying. I'm not sure what is wrong
with our linux environment. We are currently using:
Red Hat Enterprise Linux WS release 3 (Taroon Update 5)
Linux lsfnode0 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:46:36 EDT 2005 x86_64
x86_64 x86_64 GNU/Linux
*** Bug 171489 has been marked as a duplicate of this bug. ***
This looks like something for which you would be best off filing a support
ticket. In order to do so, please either contact Red Hat's Technical Support
line at 888-GO-REDHAT or file a web ticket at
http://www.redhat.com/apps/support/. Bugzilla is not an official support
channel, has no response guarantees, and may not route your issue to the
correct area to assist you. Using the official support channels above will
guarantee that your issue is handled appropriately and routed to the
individual or group which can best assist you with this issue and will also
allow Red Hat to track the issue, ensuring that any applicable bug fix is
included in all releases and is not dropped from a future update or major
Can you attach an strace -f to the xinetd when the problem starts occuring?
That might help us narrow down precisely what's going wrong.
Created attachment 120579 [details]
strace -f xinetd
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.