Bug 228149

Summary: gdm fails to start
Product: [Fedora] Fedora Reporter: R. Morton jr <friez187>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
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: 2008-03-18 18:41:17 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
screenshot none

Description R. Morton jr 2007-02-10 16:15:52 UTC 
Description of problem:

gdm fails to start
Version-Release number of selected component (if applicable):

gdm-2.16.4-1.fc6
How reproducible:

reboot system /restart deamon
Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 R. Morton jr 2007-02-10 16:15:52 UTC 
Created attachment 147836 [details]
screenshot
Comment 2 R. Morton jr 2007-02-10 17:40:40 UTC 
Feb 10 12:25:16 localhost gdm[2745]: (null): cannot open shared object file: No
such file or directory
Feb 10 12:25:19 localhost gdm[2826]: gdm_slave_greeter: Cannot start greeter
trying default: /usr/libexec/gdmlogin
Feb 10 12:25:19 localhost gdm[2826]: failsafe dialog failed (inhibitions: 0 0)
Feb 10 12:25:19 localhost gdm[2826]: failsafe dialog failed (inhibitions: 0 1)
Feb 10 12:25:19 localhost gdm[2826]: failsafe dialog failed (inhibitions: 1 1)
Feb 10 12:25:19 localhost gdm[2826]: gdm_slave_greeter: Error starting greeter
on display :0
Feb 10 12:25:20 localhost gdm[2745]: gdm_child_action: Aborting display :0
additional info
Comment 3 Ray Strode [halfline] 2008-03-18 18:41:17 UTC 
Hi,

We no longer support Fedora Core 6 and I am currently trying to get my open bug
count down to a more manageable state.  I'm going to close this bug as WONTFIX.
 If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?

(this is a mass message)