New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/27626#issuecomment-753666616

Comment:
If you really want to dig into it, you could completely disable the building in of all private libraries, figure out which private libs should be a part of `samba-libs` and which should remain in `samba`, and see if that makes a difference for your problem. (Private libraries that are required by stuff already in `samba-libs` should be in that package to avoid cyclic dependencies between `samba` and `samba-libs`, but other private libs should stay in `samba`.)

However, since the first 4.13.2 package worked for you, I wouldn't think this would be a built-in library issue.

One thing to try is totally purging `/var/{lib,cache}/samba`, `/run/samba` and maybe even `/etc/samba/private` before attempting to launch the new version, but then you'll have to recreate your password database.

Does `testparm` give you anything useful?