package winbind 2:4.10.7+dfsg-0ubuntu2.4 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1

[giri dharan]

trying to install winbind as smbd.service failes when "security=ads" set in smb.conf.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: winbind 2:4.10.7+dfsg-0ubuntu2.4
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
AptOrdering:
 winbind:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jan 23 15:32:09 2020
ErrorMessage: installed winbind package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-01-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt 1.9.4
SambaClientRegression: Yes
SourcePackage: samba
Title: package winbind 2:4.10.7+dfsg-0ubuntu2.4 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Christian Ehrhardt  (paelzer)]

Hi Giri,
this comes down to something that is special on your system.
Either the system itself or some configuration - usually the latter.

On package install/upgrade of a service it has to be (re-)started and this is what fails in this case.

As the error in your console shows you I'd encourage you start checking out the details you get with:
  See "systemctl status winbind.service" and "journalctl -xe" for details.

The default info that was attached isn't sufficient to see much further.
You can of course provide what you find when checking the above and one can try to help you here.

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]