Bug 206009

Summary: kdm: login hangs for 30 sec if network enabled but disconnected
Product: Red Hat Enterprise Linux 3 Reporter: Daniel Ganek <dan.ganek>
Component: kdebaseAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 18:41:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Ganek 2006-09-11 14:17:41 UTC
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):

 kdebase-3.1.3-5.5

How reproducible:

Steps to Reproduce:
1. Use kdm for login
2. Enable the network
3. Unplug the network cable
4. Try to login

Actual results:
Login dialog remains for about 30 sec. System then
logs the user in normally. 


Expected results:
Login should proceed promptly; i.e. in a second or two.


Additional info:
Logout hangs too.

Comment 1 Daniel Ganek 2006-09-11 20:56:16 UTC
More info:

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.



Comment 2 Daniel Ganek 2006-09-11 20:57:04 UTC
KDE says 3.1.3 is too old to fiel a BZ.



Comment 3 Daniel Ganek 2006-09-18 18:13:32 UTC
More info

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.

Comment 4 RHEL Program Management 2007-10-19 18:41:18 UTC
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:
http://www.redhat.com/security/updates/errata/
 
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.