Bug 704472

Summary: GDM won't start after upgrade from Fedora 13 to 15RC - but startx with .XClients works
Product: [Fedora] Fedora Reporter: Tomasz Ostrowski <tometzky+redhat>
Component: gdmAssignee: jmccann
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: cschalle, jmccann, pza, rstrode
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: 2011-06-03 08:37:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg output none

Description Tomasz Ostrowski 2011-05-13 09:23:58 UTC 
Description of problem:
GDM does not start. After reboot X tries to start several times then gives-up.

Logging in on text console as a user and adding ~/.XClients with:
exec startxfce4

And then issuing "startx" works.

Version-Release number of selected component (if applicable):
gdm-3.0.0-3.fc15.i686

How reproducible:
Unknown.

Steps to Reproduce (I did this, I don't know if it will reproduce):
0. Fedora 13 worked fine for about year
1. Disabled all repositories except fedora and updates
2. Removed all extra packages - only old kernel nvidia driver left, as it was running.
3. Preupgrade Fedora 15
4. Reboot, upgrade, reboot.

Actual results:
X does not work.

Expected results:
GDM login screen.

Additional info:
I'll attach dmesg after reboot.
Smolt profile: http://www.smolts.org/client/show/pub_e4bb5575-1643-4dba-89f7-6d5041ce18c8
Comment 1 Phil Anderson 2011-05-14 09:39:09 UTC 
I experienced the same after upgrading from Fedora 14.  Nothing obvious in any of the logs.

/var/log/:0-greeter.log is empty, and :0.log seems normal.

Where else should I check for hints of what might be wrong?
Comment 2 Tomasz Ostrowski 2011-05-14 09:50:15 UTC 
Created attachment 498913 [details]
dmesg output
Comment 3 Tomasz Ostrowski 2011-06-03 08:37:22 UTC 
This bug seems to be corrected by now, so I'm closing it.