package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

[Leif Johansen]

No more I can't see what was wrong!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Aug 19 16:23:07 2018
ErrorMessage: installed samba package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-03-02 (170 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 nautilus 1:3.26.3-0ubuntu4
 gvfs 1.36.1-0ubuntu1.1
SambaClientRegression: No
SourcePackage: samba
Title: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-04-27 (114 days ago)

[Andreas Hasenack (ahasenack)]

I'm going to mark this as a duplicate of #1731502.

For your specific problem, please restart the samba services after your network is established, which I believe happens after you login on your desktop.

sudo systemctl restart smbd.service nmbd.service

[Christian Ehrhardt  (paelzer)]

Hi,
it gets an timeout while waiting for interfaces.
From your log:
"nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."

Maybe a setup problem?

I never had IPV6 only samba if that is what you have.
But it could as well be just a type in what it should bind to.

Take a double check at your config.

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