From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020808
Description of problem:
the new configuration file has higher priority than local changes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. upgrade gdm
Actual Results: gdm.conf is now gdm.conf.rpmsave, so the X terminals have
stopped working, the look on people desktops is now not the company look, etc.
Expected Results: the package should install the new gdm.conf as .rpmnew.
(this has annoyed me a long time, though, especially due to bug 71308 ;-)
OK, this isn't working; we've already had two gdm bugfixes in the last
48 hours where users are left with a broken gdm if their
gdm.conf wasn't replaced. And there are theoretically security fixes
that could involve gdm.conf.
noreplace and replace policies are both broken, but in practice here replace is
going to mean fewer people with hosed systems. At least we know the default
config file will always work, and we need to be able to get changes to
people with package upgrades.
Reopening to remember to revert this change.
hmm. won't the conffile be replaced if it has been left untouched by the user,
even with a "noreplace"? if not, I guess I should file a bug against RPM :)
Sure, but anyone who's ever run gdmsetup and experimented with settings will
have touched it, right?
so is this really a blocking bug?
Changed back in 22.214.171.124-9
Fix confirmed with gdm-126.96.36.199-9.