Ubuntu
samba4 package

package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 126

Bug #1075993 reported by Armando Marques Sobrinho on 2012-11-07

This bug report is a duplicate of: Bug #988509: setoption.pl is not executable. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	samba4 (Ubuntu)	New	Undecided	Unassigned

Bug Description

when I just conclude to install using "sudo apt-get install samba4" I try to start using samba -start and then I get this error!

thanks!

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Wed Nov 7 12:29:07 2012
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 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: sub-processo script post-installation instalado retornou estado de saída de erro 126
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Armando Marques Sobrinho (marquessbr) wrote on 2012-11-07:

AptOrdering.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (611 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (158.9 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (4.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (1.3 KiB, application/x-gzip)

Revision history for this message

Robert Roth (evfool) wrote on 2012-11-07:

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 #1075804, 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.