gdm.conf-custom conffile change confusing

[wpshooter]

After installing the latest batch of updates for my FEISTY machine that were available yesterday (Tuesday, March 13, 2007), when I rebooted my machine the parameters that I had previously set and saved that caused my normal user to be automatically logged on (thereby bypassing the logon prompts), was gone because I in fact did get the prompts for both my user ID and password.

Also when subsequently going into the login windows settings, I also noticed that the parameter which I had uncheck for the login prompt sound was re-checked, when I had previously had it set to unchecked.

Were these parameters being reset by the latest updates an intention act or an oversight on someone's part ?

Thanks.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Where did you make these changes? Thanks in advance.

[wpshooter (joverstreet1)]

Made them in System, Administration, Login Window, Accessibility tab and
Security tab.

Thanks.

On Wed, 2007-03-14 at 23:01 +0000, Brian Murray wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Where did you make these changes? Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>

[Sebastien Bacher (seb128)]

Did you get an upgrade question about wether to keep your gdm.conf-custom version or the distribution one? What option did you pick?

[wpshooter (joverstreet1)]

Yes, I did get some cryptic message regarding whether to keep some type
of file or to replace and since I thought this was supposed to be
updating PROGRAMMING on my system, I choose to REPLACE.

If the meaning of this was to ask whether I wanted to keep my session
setting or to replace them back to some default state, then that's what
the prompt should have said.

Thanks.

On Thu, 2007-03-15 at 23:10 +0000, Sebastien Bacher wrote:
> Did you get an upgrade question about wether to keep your gdm.conf-
> custom version or the distribution one? What option did you pick?
>
> ** Changed in: gdm (Ubuntu)
> Sourcepackagename: control-center => gdm
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>

[Sebastien Bacher (seb128)]

The question was about using the ubuntu version or your modified config, the default option was to keep your config. We will fix that for feisty and not use any question then

[Sebastien Bacher (seb128)]

This upload fixes the bug:

 gdm (2.18.1-0ubuntu1) feisty; urgency=low
 .
   * New upstream version:
     - The GDM configuration option daemon/PidFile is now deprecated and
       GDM now always uses /var/run/gdm.pid. The location can be configured
       at compile time with the configure --with-pid-file option. This
       fixes bug #162849.
     - Now GDM supports Xephyr as the Nested Xserver command. GDM will use
       Xephyr by default if it is on the system, and fallback to Xnest. Xephyr
       works much better than Xnest.
     - GDM application desktop files now use the correct categories, so the
       menu choices should appear in the correct place in the menu.
     - Remove the userlist from the circles and happygnome themes since this
       was causing problems for some users. This change will go into 2.20
       where we are fixing the problem better by fixing gdmsetup to support
       setting the configuration so that gdmlogin and gdmgreeter work the
       same way with the Browser key.
     - Now gdmgreeter has an ATK label for the entry field.
     - Fix check so language combo style works. Fixes bug #423063.
     - Now "Configure GDM" menu choice is not available when accessibility is
       turned on since running gdmsetup in this configuration causes GDM to
       hang. Until the hanging bug is fixed, it's better to not allow the
       user to get into this situation.
     - Now support XnestUnscaledFontPath configuration option, which allows GDM
       to work with Xnest. Xorg 7.2 XGetFontPath function now returns fontpath
       with the ":unscaled" prefix, which Xsun Xnest cannot handle. Setting
       XnestUnscaledFontPath=false, will strip the ":unscaled" prefix from the
       fontpath so that it can work.
     - GDM daemon no longer links with D-Bus if ConsoleKit is not enabled.
     - Translation updates
   * debian/patches/01_xconfigoptions.patch,
     debian/patches/02_default_config.patch,
     debian/patches/04_menu_changes.patch,
     debian/patches/10_noxkeepcrashing.patch:
     - updated
   * debian/patches/06_no_conffile_diff_due_to_comment_change.patch:
     - don't change comments to gdm.conf-custom to not get a conffile change
       on upgrade (Ubuntu: #92302)