Bug 453301

Summary: gdm-2.22.0-7.fc9 is broken completely refuses to start
Product: [Fedora] Fedora Reporter: David <webmaster>
Component: gdmAssignee: jmccann
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: low    
Version: 9CC: cschalle, farrellj, 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-30 17:51:11 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
Logentries from startup with new gdm none

Description David 2008-06-29 09:29:25 UTC
Description of problem:
gdm-2.22.0-7.fc9 is broken completely refuses to start

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 David 2008-06-29 09:31:14 UTC
Sorry I meant for Fedora 9 not 8.  gdm-2.22.0-7.fc9 is no good but atleast -6
worked...  How soon until a -8 can be put out?

Its critical as if you update gdm in updates-testing your box is then broken.

Comment 2 Stefan Neufeind 2008-06-29 10:32:38 UTC
I can confirm an update from 2.22.0-5 to 2.22.0-7 (updates-testing) broke gdm
for me as well. Attaching a log from /var/log/messages - maybe that helps.

Comment 3 Stefan Neufeind 2008-06-29 10:33:11 UTC
Created attachment 310535 [details]
Logentries from startup with new gdm

Comment 4 Jason Farrell 2008-06-29 14:49:21 UTC
Can confirm here as well.

This release was supposed to add back "autologin support" (which I don't use),
and I note that I saw 5 (or 6) instances of Xorg and various gnome-* daemons
running, when only one was expected.

Comment 5 Ray Strode [halfline] 2008-06-30 17:51:11 UTC
Should be fixed in -8,


*** This bug has been marked as a duplicate of 453309 ***