From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030115
Description of problem:
Upgrading the "gdm" package seems to reset the settings to default. This can
potentially cause confusion when upgrading "gdm" for LTSP servers, because XDMCP
I noticed this behavior when upgrading between the following packages, so I
suspect this is generally the case with gdm packaging.
gdm-188.8.131.52-14.i386.rpm to gdm-184.108.40.206-1.i386.rpm
gdm-220.127.116.11-1.i386.rpm to gdm-18.104.22.168-1.i386.rpm
Steps to Reproduce:
1. Set gdm settings, like XDMCP.
2. Upgrade gdm.
Settings are reset to default.
Settings should be kept.
I'm almost sure we went through this for 8.0 betas - changing it to noreplace,
observing that stuff broke, and changing it back. The problem is that if you
don't upgrade the config you often don't get bugfixes.
There's just an inherit tradeoff: replace and get people bugfixes but make
them manually restore their local mods, or don't replace and don't get out
the bugfixes. There is no correct answer, both ways have a major downside...
I think it's best to just pick one and stick to it.