Bug 2471 - GDM sometimes fails to start services after reboot.
GDM sometimes fails to start services after reboot.
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jonathan Blandford
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-01 16:07 EDT by shane
Modified: 2013-04-02 00:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-19 16:48:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description shane 1999-05-01 16:07:23 EDT
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 11:53:59 EDT
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 16:48:59 EDT
closed; lack of input

Note You need to log in before you can comment on or make changes to this bug.