package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2 failed to install/upgrade: Unterprozess installed samba package post-installation script gab den Fehler-Ausgangsstatus 1 zurück

[Horst Seeger]

already before this problem had existed. So in dist. 17.10 maybe even 17.04 I had removed samba to avoid those problems. But I would like to have it to communicate in our home-net.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: samba 2:4.7.6+dfsg~ubuntu-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_30_32_generic_42
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libarchive13:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Aug 15 10:48:57 2018
ErrorMessage: Unterprozess installed samba package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2017-12-19 (239 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 failed to install/upgrade: Unterprozess installed samba package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: Upgraded to bionic on 2018-04-19 (119 days ago)

[Christian Ehrhardt  (paelzer)]

Hallo,
your log essentially show s it failing due to a bad configuration:
  Unable to locate guest account [smbguest]!
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.

I assume you have enabled something like this in your /etc/smb.conf
   guest account = GibtEsNicht

Essentially juts a user that doesn't exist.
This is not in the default config.

That is a broken config, you'd either have to remove that section and overall clean up your smb.conf or you have to make sure it works by creating the user as needed.

If you have no custom samba conf that you have to retain you can most easily get back to a default config with:
$ apt remover --purge samba samba-common
$ apt install samba

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