Red Hat Bugzilla – Bug 206009
kdm: login hangs for 30 sec if network enabled but disconnected
Last modified: 2007-11-30 17:07:10 EST
Description of problem:
If the network is enabled but the network is disconencted; e.g., the cable
unplugged, user login hangs for 30 seconds. it doesn't matter if
a) nfs or amd is enabled or not
b) using a static IP address or DHCP
c) which desktop the user uses: one of our users uses mwm.
Neither gdm nor unix login(i.e., run level 3) exhibit this problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use kdm for login
2. Enable the network
3. Unplug the network cable
4. Try to login
Login dialog remains for about 30 sec. System then
logs the user in normally.
Login should proceed promptly; i.e. in a second or two.
Logout hangs too.
Using strace I determined the a child of kmd; i.e. "-:0" is querying
the DNS servers and it's takes awhile for these queries to time out.
KDE says 3.1.3 is too old to fiel a BZ.
One of our name servers went down and kdm now hangs even if the network
is connected. So, it looks like kdm is requiring a response from ALL
name servers not just one.
I removed the ip address of the missing name servers and login worked as it should.
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.