package samba 2:4.6.7+dfsg-1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nahid.sayem]

when i'm updating my system after fresh install of Ubuntu Budgie 17.10 the package (package samba 2:4.6.7+dfsg-1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1) as you see it's not installing or i'm not able to install any apps from the ubuntu app store .......app store says (Sorry Something went wrong)....THANKS.....

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: samba 2:4.6.7+dfsg-1ubuntu3.2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
BothFailedConnect: Yes
Date: Fri Mar 30 16:17:39 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
NmbdLog:

Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5.1
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
TestparmExitCode: 0
Title: package samba 2:4.6.7+dfsg-1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Christian Ehrhardt  (paelzer)]

From your log:
Job for nmbd.service failed because a timeout was exceeded.
See "systemctl status nmbd.service" and "journalctl -xe" for details.
...
"nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ...

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

You can either fix your config (to have the service working and therefore work restarting on upgrades) OR purge it (better than keeping around misconfigured anyway).

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.

[Andreas Hasenack (ahasenack)]

I believe this is a duplicate of #1731502