Bug 85084

Summary: GNOME login session hangs
Product: [Retired] Red Hat Public Beta Reporter: Michael Wardle <michael.wardle>
Component: gnome-desktopAssignee: Mark McLoughlin <markmc>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: phoebe   
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: 2003-02-25 15:33:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Wardle 2003-02-25 15:01:26 UTC
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): 
gnome-desktop-2.2.0.1-3 
 
How reproducible: 
Always 
 
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 
happens. 
 
Expected results: 
Icons appear along the bottom of the splash screen to indicate 
progress. 
 
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 
fine. 
Networking is correctly configured, and the host's host name can be 
resolved (using DNS).

Comment 1 Michael Wardle 2003-02-25 15:33:38 UTC
After another reboot, the problem no longer exhibits itself.