Red Hat Bugzilla – Bug 173933
a modified gdm conf file prevents gdm from starting after modular X upgrade
Last modified: 2007-11-30 17:11:17 EST
Description of problem:
If you have a modified gdm conf file it's not replaced when gdm is upgraded and
it contains a path to the X server. Since the X server location has moved gdm
won't start up after a modular X upgrade.
Steps to Reproduce:
1. Modify your gdm.conf
2. Update to test1 (with modular X)
3. Note that gdm won't start with next boot
Warning about failing to start the X server
X Starts up.
I think the best way to do this for now, is to have gdm hard code
/usr/bin/X which is the symlink pointing to the X server. Now that
we're packaging X in FHS locations, it is highly probable that the
symlink will always be there. I think I can almost guarantee it. ;)
Ray, what do you think? kdm used to use Imake to find out where the
X server was, but that's broke now. If you think autodetection is still
useful for this, we can probably get xorg to put a pkg-config variable
in the pc file. That might be the best long-term solution.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)