Bug 408371

Summary: Upgrade from F7 to F8 stops GDM from working
Product: [Fedora] Fedora Reporter: Nigel Horne <njh>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8   
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: 2007-12-04 04:11: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:
Embargoed:

Description Nigel Horne 2007-12-03 07:51:50 UTC 
Description of problem:
I just get a black screen with a mouse pointer


Version-Release number of selected component (if applicable):
gdm-2.20.1-7.fc8

How reproducible:
100%

Steps to Reproduce:
1. Upgrade to F8
2. Reboot
3.
  
Actual results:
See above

Expected results:
Login screen

Additional info:

/var/log/secure keeps being appended to with cryptic messages such as:

Dec  3 07:50:26 njh gdm-binary[586]: pam_selinux_permit(gdm:auth): Cannot
determine the user's name
Dec  3 07:50:26 njh gdm-binary[586]: gkr-pam: couldn't get the user name:
Conversation error
Comment 1 Ray Strode [halfline] 2007-12-03 17:07:14 UTC 
It seems like your authentication stack might be messed up.  Does logging in
from a console work?

Can you attach /etc/pam.d/system-auth ?

if you add 

*.* /var/log/debug_messages

to /etc/rsyslog.conf and then do /sbin/service rsyslog restart then try to
reproduce do you get more useful messages in /var/log/debug_messages ?
Comment 2 Nigel Horne 2007-12-03 17:13:34 UTC 
Yes, login from console works.

I'll try the other suggestions.
Comment 3 Ray Strode [halfline] 2007-12-03 17:28:40 UTC 
Cool, thanks.
Comment 4 Nigel Horne 2007-12-03 20:13:25 UTC 
I found that by reinstalling gdm

rpm -Uvh --force gdm-2.20.1-7.fc8.i386.rpm

it now works. Presumably something had corrupted one of the program's files.
Let's hope it doesn't happen again.
Comment 5 Ray Strode [halfline] 2007-12-04 04:11:22 UTC 
okay, i'm going to close this WORKSFORME.  We haven't had any other reports so
it may have just be corrupted media or a phase-of-the-moon type thing.