package samba-common-bin 2:4.15.13+dfsg-0ubuntu1.1 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 127

[Thomas]

Settings wasn't functioning after reinstall and upgrade to 22.04, suggested fix was to reinstall gnome-control-center, got samba error. Tried to install samba, got a dependency error, samba-common-bin,
Setting up samba-common-bin (2:4.15.13+dfsg-0ubuntu1.1) ...
Checking smb.conf with testparm
testparm: symbol lookup error: /usr/lib/x86_64-linux-gnu/samba/libldbsamba.so.0: undefined symbol: ldb_msg_element_is_inaccessible, version LDB_2.4.4
dpkg: error processing package samba-common-bin (--configure):
 installed samba-common-bin package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of samba:
 samba depends on samba-common-bin (= 2:4.15.13+dfsg-0ubuntu1.1); however:
  Package samba-common-bin is not configured yet.

dpkg: error processing package samba (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 samba-common-bin
 samba

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: samba-common-bin 2:4.15.13+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jun 9 10:02:25 2023
ErrorMessage: installed samba-common-bin package post-installation script subprocess returned error exit status 127
InstallationDate: Installed on 2023-05-05 (34 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
Python3Details: /usr/local/bin/python3.10, Python 3.10.6, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
 nautilus 1:42.6-0ubuntu1
 gvfs 1.48.2-0ubuntu1
SambaClientRegression: Yes
SourcePackage: samba
Title: package samba-common-bin 2:4.15.13+dfsg-0ubuntu1.1 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

[Robie Basak (racb)]

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

This looks like local corruption or misconfiguration, rather than a bug in Ubuntu. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

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 rather than a problem specific to your system, and then change the bug status back to New.

Without steps to reproduce the problem, there is little that can be done on this bug. I'll mark this bug as Incomplete for now, pending someone else confirming that it is a bug or unless someone can provide steps to reproduce.

Please do report any other bugs you may find.

[RedScourge (redscourge)]

I just got this same thing on 22.04.1 after trying to install the Samba updates in jammy-proposed which was prescribed for fixing the Ubuntu Bug #2027716 entitled "samba dc ntlm netlogin issue with windows 10/11 2023-07 cumulative update".

I cannot figure out how to resolve the bug by reverting, as the same error appears when reverting too.

[RedScourge (redscourge)]

on a hunch I tried reinstalling every package that seemed to have to do with the LDB library, which was ldb-tools libldb2 and python3-ldb, and it seems to have resolved it for me.

[Thomas (ttwettlaufer)]

ok, I just tried reinstalling the tools, but it didn't help. Did get help from folks on the chat channel and fixed a couple other items, which fixed some other problems related to this issue but not this issue specifically. I will work on this more later. thanks.

[Thomas (ttwettlaufer)]

ok, I finally gave up and reinstalled everything. Fortunately, I keep my /home on a separate drive, so it mostly worked out fine.

[Lucas Kanashiro (lucaskanashiro)]

Could anyone affected provide reproduction steps for this issue? I tried a regular upgrade in Jammy and it worked just fine. Maybe you have some local config that might be triggering the issue for you (?)

[Andreas Hasenack (ahasenack)]

The bug description has this line:

Python3Details: /usr/local/bin/python3.10, Python 3.10.6, unpackaged

Which tells us that that installation was not using python as shipped by ubuntu.

Regarding what others are reporting, we definitely need more information to diagnose this, but I would suggest to check if there are python modules or installations from outside ubuntu, and if all samba binary packages were updated, and not just some.

For reference, these are all the binary samba packages in jammy:

samba samba-libs samba-common samba-common-bin smbclient samba-testsuite registry-tools samba-dev python3-samba samba-dsdb-modules samba-vfs-modules libsmbclient libsmbclient-dev winbind libpam-winbind libnss-winbind libwbclient0 libwbclient-dev ctdb

So check if they are all at the same version:

dpkg -l | grep -E '(samba|samba-libs|samba-common|samba-common-bin|smbclient|samba-testsuite|registry-tools|samba-dev|python3-samba|samba-dsdb-modules|samba-vfs-modules|libsmbclient|libsmbclient-dev|winbind|libpam-winbind|libnss-winbind|libwbclient0|libwbclient-dev|ctdb)'

Note that ldb has the samba version embedded in its full version.

[Launchpad Janitor (janitor)]

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