Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2471

Summary: GDM sometimes fails to start services after reboot.
Product: [Retired] Red Hat Linux Reporter: shane
Component: gdmAssignee: Jonathan Blandford <jrb>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.0CC: ddumas
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-08-19 20:48:16 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 shane 1999-05-01 20:07:23 UTC 
60% of the time GDM will fail to bring up
enlightenment/gnome after a reboot.  I will be forced to hit
CTRL ALT BACKSPACE and relogin.  After the inital hang,
things proceed normally.  I would guess it is related to the
increased time needed to start enlightenment/gnome the first
time as they are not cached.
Comment 1 Michael K. Johnson 1999-05-11 15:53:59 UTC 
Let me make sure this is clear: you try to log in and the login
process hangs after you have entered your login name and password?
What does the screen look like at this point?  Is the Red Hat logo
still showing, for example?  Have you checked the logs to see if
any error messages are showing up?  gdm logs X output in /var/gdm;
in your case, the contents of /var/gdm/:0.log would be interesting.
During the hang, go to a text console with ctrl-alt-F1, log in as
root, and copy the contents of /var/gdm/:0.log somewhere and mail
them back to bugzilla (respond to the email containing this message).
Comment 2 Bill Nottingham 1999-08-19 20:48:59 UTC 
closed; lack of input