gdm monitors for $HOME/.face even when IncludeAll is false

the bug has been fixed upstream now

let's nominate for lucid it seems worth getting in a stable update

As part of the usual LTS approach of SRUing GNOME bug fix microreleases I prepared an update to gdm 2.30.2 which fixes this problem. I uploaded the package to the desktop PPA for now: https://launchpad.net/~ubuntu-desktop/+archive/ppa

For testing, you can do

  sudo add-apt-repository ppa:ubuntu-desktop/ppa
  sudo apt-get update
  sudo apt-get upgrade

Early feedback appreciated!

This is the debdiff between 2.30.0 (in lucid) and 2.30.2, with autoconf noise and po file changed removed.

I tested it locally with both manual and autologin, on two different computers (the other one using the ubuntu-desktop PPA)

Please note that the version actually uploaded to lucid-proposed now also fixes bug 398300 and thus has two more changes which are described in that bug.

Accepted into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

This bug was fixed in the package gdm - 2.30.2-0ubuntu1

---------------
gdm (2.30.2-0ubuntu1) lucid-proposed; urgency=low

  * New upstream bug fix release:
    - Accessibility is now enabled by default for the GDM login screen.
    - When the face browser is disabled, the PAM conversation is started
      immediately, so users do not need to click a button to start entering
      the username and password. (GNOME #591082)
    - Add label-for and labelled-by a11y relations to the entry field in the
      login GUI. This makes the login GUI more accessible when using AT programs.
      (GNOME #613434).
    - Fixed bugs that were causing XDMCP to not show the greeter again after
      logout. (GNOME #606724).
    - The default XDMCP PingIntervalSeconds was increased from 15 to
      60 seconds.
    - The WINDOWPATH environment variable is now set for the user session.
      (GNOME #609272)
    - Ensure Init script is called when using Automatic Login. (GNOME #614488)
    - Fix race condition with Timed Login. (GNOME #614062)
    - Drop xhost localuser:gdm and localuser:root when the user session starts.
      (GNOME #605350)
    - Removed the icon monitor from the GDM login GUI since it was not functional
      and was causing problems with automounting user's $HOME directories.
      (GNOME #609321, LP: #518810)
    - Do not mark "%x" for translation. (GNOME #613306)
    - Remove duplicated strings for translation. (GNOME #609179)
    - Minor doc corrections.
    - Translation updates.
  * 04_fix_external_program_directories.patch, 99_autoreconf.patch: Refresh
    for new upstream version.
  * Add 34_disable_a11y_default.patch: Revert upstream change between 2.30.0
    and 2.30.1 to enable a11y by default. This wasn't tested and isn't
    appropriate for an SRU.
  * 06_run_xsession.d.patch: Export $USERXSESSION, $USERXSESSIONRC, and
    $ALTUSERXSESSION, so that running the "custom"/"default" sessions actually
    works. Without those, /etc/X11/Xsession.d/50x11-common_determine-startup
    decides to run the system default session even if we have the
    "allow-user-xsession" option. This is a prerequisite for fixing LP#398300.
    Also update the patch tag header to comply to DEP-3.
  * Add debian/xsession.desktop: Add a new session type "~/.xsession" which
    will run ~/.xsession (Exec=default will be interpreted by the
    20x11-common_process-args and 50x11-common_determine-startup Xsession.d
    scripts). If the admin sets "allow-user-xsession" to False, this will
    launch the system default session instead. (LP: #398300)
 -- Martin Pitt <email address hidden> Wed, 28 Apr 2010 14:41:12 +0200

Copied lucid-proposed to maverick.

The package in lucid-proposed breaks users who set disable_user_list to true. The result is that you still get a Log In button (which the changelog indicates shouldn't happen anymore) but when you click it, GDM crashes. Reverting to the version in Lucid main resolved the issue.

See bug 579044 for details of the regression.

There is a new candidate lucid update which has been uploaded now, the debdiff is on bug #585574

Accepted gdm into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

could you test the new update version?

Thank you for your efforts on this, but unfortunately I'm a bit too busy to test this until the end of the month. So wait two weeks and I'll let you know how it works :)

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".