Comment 13 for bug 546874

Revision history for this message
Thierry Carrez (ttx) wrote :

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...