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