I understand the status of this is invalid; however, my organization has a number of Ubuntu Servers that suffer from the same problem. This only happens with Ubuntu 18.04 and it causes problems, especially when attempting to automate package installation and server configurations on a large scale.
After some exploration, it appears the problem may be in the postinst script of the winbind package itself. The first part of the code adds the 'winbindd_priv' group and creates the /var/lib/samba/winbind_privileged socket directory. Then (and this is where I have a question), it checks to see if the /etc/init.d/winbind file exists. If it does, it proceeds to configure the init.d start/stop processes with update-rc.d followed by attempting to either start (if a new build) or restart (if an upgrade) the service. This is where the failure is occurring because winbind for Ubuntu 18.04 is supposed to be using systemd and is conflicted when attempting to set up the two. One of the ways I was able to get this to work was to simply remove the /etc/init.d/winbind file and run dpkg --configure winbind. The install completed without any further issues and shows that this is where the pain point is. My question is, other than "backwards compatibility" (which we should be well past now), why is there a need to configure the init.d start/stop routines if 18.04 uses systemd? Can the init.d scripting be removed from future packages for Ubuntu so this type of issue doesn't crop up again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787834 Title: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1787834/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
