Bug 85084 - GNOME login session hangs
GNOME login session hangs
Product: Red Hat Public Beta
Classification: Retired
Component: gnome-desktop (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Mark McLoughlin
Depends On:
  Show dependency treegraph
Reported: 2003-02-25 10:01 EST by Michael Wardle
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-25 10:33:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Wardle 2003-02-25 10:01:26 EST
Description of problem: 
When selecting a Default or GNOME session login from gdm and logging in as a 
normal user, the Red Hat GNOME splash screen appears, but no progress is made 
for over a minute. 
Version-Release number of selected component (if applicable): 
How reproducible: 
Steps to Reproduce: 
1. Perform fresh install of Red Hat Linux 8.0.94 
2. Create a user account 
3. Start GDM (or enter runlevel 5) 
4. Leave the Default session type selected (or select GNOME) 
5. Enter the user's username and password 
Actual results: 
A blue splash screen appears with the Red Hat logo, then nothing 
Expected results: 
Icons appear along the bottom of the splash screen to indicate 
Additional info: 
This happened on a clean install of Red Hat Linux 8.0.94 (phoebe-3). 
I chose to install GNOME and KDE. 
I have tried rebooting, but to no avail. 
No errors appear either on the screen or in .xsession-errors, nor when 
starting "gnome-session" in the xterm provided by a Failsafe X session. 
.gconf, .gconfd, .gnome, .gnome2, .gnome2_private directories are 
created in the user's home directory. 
KDE is also installed.  When selecting the KDE session, KDE works 
Networking is correctly configured, and the host's host name can be 
resolved (using DNS).
Comment 1 Michael Wardle 2003-02-25 10:33:38 EST
After another reboot, the problem no longer exhibits itself.

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