This bug was fixed in the package pam - 1.1.3-10ubuntu1
---
pam (1.1.3-10ubuntu1) trusty; urgency=low
* Merge from Debian unstable, remaining changes:
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's
not present there or in
Yes, of course.
Here they are.
** Attachment added: pam-configs.tgz
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1160288/+attachment/3644434/+files/pam-configs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, I've been able to reproduce the problem now, though it's rather
tricky - it requires both the libpam-sss package and the mkhomedir
profile that you have available locally, in order to reproduce this.
(It seems that the sss profiles you have on your system come from
precise-updates and
I think this should do the job:
--- debian/local/pam-auth-update2011-10-30 19:06:55 +
+++ debian/local/pam-auth-update2013-04-15 19:06:23 +
@@ -686,7 +686,7 @@
} else {
chomp;
s/^\s+//;
-
The output of pam-auth-update:
$ sudo pam-auth-update
Use of uninitialized value $3 in split at /usr/sbin/pam-auth-update line 623,
CURRENT line 32.
Use of uninitialized value $curmod in quotemeta at /usr/sbin/pam-auth-update
line 631, CURRENT line 32.
Use of uninitialized value $curmod in
You appear to have a /usr/share/pam-config/mkhomedir file which doesn't
come from any Ubuntu package. Could you please attach this file as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160288
(there's also a /usr/share/pam-config/sss-password that's not packaged;
I'm pretty sure the problem is with the mkhomedir' profile, but maybe
you want to attach both of these while you're at it)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the patch, but that's not a correct fix. $3 is never
supposed to be unset here, so the root error is somewhere else.
I also can't reproduce the problem with your provided test case. You
must have previous pam-auth-update settings in your environment that are
contributing to the
