package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 126

[Baxtiyor Maxsudov]

cannot install samba4
Traceback (most recent call last):
  File "/usr/bin/samba-tool", line 26, in <module>
    from samba.netcmd.main import cmd_sambatool
  File "/usr/lib/python2.7/dist-packages/samba/netcmd/main.py", line 23, in <module>
    from samba.netcmd.dbcheck import cmd_dbcheck
  File "/usr/lib/python2.7/dist-packages/samba/netcmd/dbcheck.py", line 23, in <module>
    from samba.auth import system_session
ImportError: libauth4.so: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/usr/bin/samba-tool", line 26, in <module>
    from samba.netcmd.main import cmd_sambatool
  File "/usr/lib/python2.7/dist-packages/samba/netcmd/main.py", line 23, in <module>
    from samba.netcmd.dbcheck import cmd_dbcheck
  File "/usr/lib/python2.7/dist-packages/samba/netcmd/dbcheck.py", line 23, in <module>
    from samba.auth import system_session
ImportError: libauth4.so: cannot open shared object file: No such file or directory

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Mon May 7 09:38:28 2012
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 126
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: samba4
Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 126
UpgradeStatus: No upgrade log present (probably fresh install)

[Javier López (javier-lopez)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #988509, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad