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 #1083650 reported by Marcelo Vieira da Luz on 2012-11-27

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

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-33.52-generic-pae 3.2.31
Uname: Linux 3.2.0-33-generic-pae i686
ApportVersion: 2.0.1-0ubuntu15
Architecture: i386
Date: Tue Nov 27 13:47:57 2012
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 126
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
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

Marcelo Vieira da Luz (marvdaluz) wrote on 2012-11-27:

AptOrdering.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (390 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (53.0 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (18.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (1.4 KiB, application/x-gzip)

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2012-11-28:

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.