Bug 450541

Summary: gdm won't start
Product: [Fedora] Fedora Reporter: Bill C. Riemers <briemers>
Component: gdmAssignee: jmccann
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 9CC: cschalle, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-09 13:59:01 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:
Attachments:
Description Flags
/var/log/gdm/:0.log
none
/var/log/gdm/:0-greeter.log none

Description Bill C. Riemers 2008-06-09 13:50:38 UTC 
Description of problem:

When turning on my computer this morning, gdm was unable to start.   It would
attempt to start for about 10 seconds and then recycling.   I switched to
virtual console 1 and attempted to login, but everytime I started to type my
password it would be interrupted by gdm restarting.  After several tried I
finally managed to login and switch to run level 3.  I tried several things to
fix the problem including "yum remove gdm;yum install gdm" but the problem persists.


Version-Release number of selected component (if applicable):


How reproducible:

100% on my system

Steps to Reproduce:
1. start run level 5.
2.
3.
  
Actual results:

gdm keeps recycling

Expected results:

I should be able to login.

Additional info:

This worked normally on Friday...  I will attach relevant log files.   Even a
work around would be greatly appreciated.  I had to boot to Fedora 8 to access
bugzilla and enter this bug report.
Comment 1 Bill C. Riemers 2008-06-09 13:53:20 UTC 
Created attachment 308685 [details]
/var/log/gdm/:0.log
Comment 2 Bill C. Riemers 2008-06-09 13:53:46 UTC 
Created attachment 308686 [details]
/var/log/gdm/:0-greeter.log
Comment 3 Bill C. Riemers 2008-06-09 13:59:01 UTC 
I found the problem.  Somehow the permissions on my /tmp directory were messed
up by the tests I did yesterday reproducing an rsync bug.