pam-auth-update duplicates Additional block every time I run it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Every time I run pam-auth-update (no matter what the options, and even if I cancel the debconf prompt), it duplicates the pam_smbpass and pam_ecryptfs items in the Additional block in /etc/pam.
$ sudo DEBCONF_
debconf (developer): frontend started
debconf (developer): Trying to find a templates file..
debconf (developer): Trying /usr/sbin/
debconf (developer): Trying /usr/share/
debconf (developer): Couldn't find a templates file.
debconf (developer): frontend running, package name is
debconf (developer): starting /usr/sbin/
debconf (developer): <-- VERSION 2.0
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB backup
debconf (developer): --> 0 multiselect escape backup
debconf (developer): <-- X_LOADTEMPLATEFILE /var/lib/
debconf (developer): --> 0
debconf (developer): <-- SUBST libpam-
debconf (developer): --> 0
debconf (developer): <-- SUBST libpam-
debconf (developer): --> 0
debconf (developer): <-- FSET libpam-
debconf (developer): --> 0 false
debconf (developer): <-- SET libpam-
debconf (developer): --> 0 value set
debconf (developer): <-- INPUT high libpam-
debconf (developer): --> 0 question will be asked
debconf (developer): <-- GO
debconf (developer): --> 30 backup
debconf (developer): <-- GET libpam-
debconf (developer): --> 0 unix, smbpasswd-migrate, ecryptfs-utils, smbpasswd-migrate, ecryptfs-utils
debconf (developer): <-- FSET libpam-
debconf (developer): --> 0 false
debconf (developer): <-- SET libpam-
debconf (developer): --> 0 value set
debconf (developer): <-- FSET libpam-
debconf (developer): --> 0 false
debconf (developer): <-- SET libpam-
debconf (developer): --> 0 value set
I'm attaching a tarball containing /etc/pam.d/common-* (before this breakage), /usr/share/
I think this is critical because when those items are duplicated it renders me unable to log in (gnome-screensaver apparently hung, and login segfaulted; I had to reboot).