Comment 8 for bug 303515

I am running Jaunty Alpha 3 on a vmware install and do not have this problem. I know that I do have this problem on my Intrepid install at home. Both are updated with the latest updates.
I have the following versions of passwd and gnome-screensaver installed.

sudo apt-cache policy gnome-screensaver
gnome-screensaver:
  Geïnstalleerd: 2.24.0-0ubuntu4
  Kandidaat: 2.24.0-0ubuntu4
  Versietabel:
 *** 2.24.0-0ubuntu4 0
        500 http://nl.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

sudo apt-cache policy passwd
passwd:
  Geïnstalleerd: 1:4.1.1-6ubuntu2
  Kandidaat: 1:4.1.1-6ubuntu2
  Versietabel:
 *** 1:4.1.1-6ubuntu2 0
        500 http://nl.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

And this is the contents of my /etc/pam.d/passwd and /etc/pam.d/common-passwd
peter@test-desktop:~$ cat /etc/pam.d/passwd
#
# The PAM configuration file for the Shadow `passwd' service
#

@include common-password

peter@test-desktop:~$ cat /etc/pam.d/common-passwd
cat: /etc/pam.d/common-passwd: Bestand of map bestaat niet
peter@test-desktop:~$ cat /etc/pam.d/common-password
#
# /etc/pam.d/common-password - password-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define the services to be
# used to change user passwords. The default is pam_unix.

# Explanation of pam_unix options:
#
# The "sha512" option enables salted SHA512 passwords. Without this option,
# the default is Unix crypt. Prior releases used the option "md5".
#
# The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in
# login.defs.
#
# See the pam_unix manpage for other options.

# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules. See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
password [success=1 default=ignore] pam_unix.so obscure sha512
# here's the fallback if no module succeeds
password requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password required pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config

I can check my passwd and common-password on my intrepid install at home and see what's the case there.

Tux