Red Hat Bugzilla – Bug 167087
FC4 gdm.conf broke FC5 gdm
Last modified: 2007-11-30 17:11:12 EST
Description of problem:
GDM has been notorious through its existence for breaking upon upgrades due to
config file changes. We were again bitten by this in Jens' FC4 to rawhide
upgrade, where his gdm failed to work.
We are stuck between two conflicting requirements:
1) Allow custom options to continue working after upgrades.
2) gdm should actually work after upgrades.
Bug #135510 described a robust solution to this problem, but it would require a
good amount of upstream work to make into a reality.
Version-Release number of selected component (if applicable):
Honestly I think you've come up with an overengineered solution. The
configuration file doesn't change that much anymore. I think we should just try
making it %config(noreplace) again.
Uh... you do realize that "noreplace" guarantees that the old config file will
never be replaced by the new RPM?
This keeps breaking with new gdm upgrades because of gdm upstream's bad design. =(
IIRC, it's currently config(replace) and so people have to keep modifying their
settings every upgrade.
Wait, what is Jen's problem?
1) he upgraded and lost his settings (what i thought)
2) he upgraded and then copied his old config file on top of the newly made
config file and stuff broke (what I'm thinking may have happened now)
This has been in NEEDINFO for a long time without any feedback, closing.