There seem to be two issues:
* one is about the profile itself, which apparently breaks pam config when
enabled
* the other is about winbind.{postinst,prerm} not calling "pam-auth-update
--package" to enable/disable the profile (which is marked Default:yes, so it
will get enabled by the next pam-auth-update run ?)
I'd argue the pam_winbind profile could be "Default: no" since most
people get winbind installed when installing wine, and don't care so
much about winbind PAM integration. Those who care usually read
documentation...
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
