Bug 250657

Summary: gdmsetup will not launch in Gnome.
Product: [Fedora] Fedora Reporter: Greg Douglas <gregory.douglas>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 7CC: triage
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-17 02:04:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Greg Douglas 2007-08-02 18:49:27 UTC
Description of problem:

After upgrading from FC6, when trying to launch gdmsetup from Gnome, I get a
popup error message "GDM (The Gnome Display Manager) is not running".  I am
running Gnome, and not KDM.  I am also in Run Level 5. Gnome is my default dm.

When launched from the Gnome Terminal, I get:

[greg@atomic ~]$ gdmsetup
  Failed to connect to socket, sleep 1 second and retry
  Trying failed command again.  Try 2 of 5.
  Failed to connect to socket, sleep 1 second and retry
  Trying failed command again.  Try 3 of 5.
  Failed to connect to socket, sleep 1 second and retry
  Trying failed command again.  Try 4 of 5.
  Failed to connect to socket, sleep 1 second and retry
  Trying failed command again.  Try 5 of 5.
  Command failed 5 times, aborting.
Could not access configuration key <daemon/PidFile=/var/run/gdm.pid>
Using compiled in value </var/run/gdm.pid> for <daemon/PidFile=/var/run/gdm.pid>

Version-Release number of selected component (if applicable): gdm-2.18.0-14.fc7

How reproducible: Every Time I launch it.

Steps to Reproduce:
1. From the Gnome Menu, System > Adminstration > Login Screen
2. or from the Gnome Terminal: $ gdmsetup
Actual results:
Please see above

Expected results:
The GDM Setup panel should appear

Additional info:

Comment 1 Greg Douglas 2007-08-03 18:05:09 UTC
Just updated gdm to gdm-2.18.4-1.fc7, but the problem still persists.

Comment 2 Bug Zapper 2008-05-14 13:50:41 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2008-06-17 02:04:51 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.