Bug 408371 - Upgrade from F7 to F8 stops GDM from working
Upgrade from F7 to F8 stops GDM from working
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-12-03 02:51 EST by Nigel Horne
Modified: 2007-12-03 23:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-03 23:11:22 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 Nigel Horne 2007-12-03 02:51:50 EST
Description of problem:
I just get a black screen with a mouse pointer

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

How reproducible:

Steps to Reproduce:
1. Upgrade to F8
2. Reboot
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 12:07:14 EST
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 12:13:34 EST
Yes, login from console works.

I'll try the other suggestions.
Comment 3 Ray Strode [halfline] 2007-12-03 12:28:40 EST
Cool, thanks.
Comment 4 Nigel Horne 2007-12-03 15:13:25 EST
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-03 23:11:22 EST
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.

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