Came across this issue just last night and found the cause to be less than insidious.
Seems that after I finished editing smb.conf, the daemon reloaded the new file automagically. This is when the trouble started. As it turns out, my new config had a typo and was specifying a directory that did not exist. I believe this is what was causing samba to go tango-uniform and thus causing pam to segfault. One boot into recovery mode and a restore to the default smb.conf later, and all is well again. I will be editing my smb.conf under a different name until it has passed testparm. I will report back should another fail occur. -- segfault in pam_smbpass.so https://bugs.launchpad.net/bugs/303458 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
