Bug 82545

Summary: gdm upgrade resets settings
Product: [Retired] Red Hat Public Beta Reporter: Warren Togami <wtogami>
Component: gdmAssignee: Havoc Pennington <hp>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebe   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-23 15:06:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Warren Togami 2003-01-23 09:50:37 UTC
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
becomes disabled.

I noticed this behavior when upgrading between the following packages, so I
suspect this is generally the case with gdm packaging.
gdm- to gdm-
gdm- to gdm-

How reproducible:

Steps to Reproduce:
1. Set gdm settings, like XDMCP.
2. Upgrade gdm.
Actual Results:  
Settings are reset to default.

Expected Results:  
Settings should be kept.

Comment 1 Havoc Pennington 2003-01-23 15:06:46 UTC
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.