I can confirm the problem reported originally in this bug (all those segfaults after the upgrade) only happen if you have winbind listed first, ahead of files or compat.
Any particular reason why that order was chosen? There will for sure be a "blip" in the winbind service during the upgrade, and having the system users fail to be resolved is bound to be catastrophic. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1584485 Title: Upgrading samba to latest security fixes together with winbind in nsswitch.conf can harm entire OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/+subscriptions -- 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
