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 #1061295 reported by Rafael Gomes on 2012-10-03

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

all installations have failled because this issue

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic i686
ApportVersion: 2.0.1-0ubuntu13
AptOrdering:
mesa-utils: Install
samba4: Configure
mesa-utils: Configure
Architecture: i386
Date: Wed Oct 3 18:43:35 2012
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 126
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
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: Upgraded to precise on 2012-10-03 (0 days ago)

Tags:

Revision history for this message

Rafael Gomes (rafaelgomesdm) wrote on 2012-10-03:

Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (323 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (124.0 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (84.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2012-10-04:

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.