Ubuntu
samba4 package

error 126 installing

Bug #1093913 reported by Matias Fernandez on 2012-12-26

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

This bug affects 2 people

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

Bug Description

error on install

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
Uname: Linux 3.2.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: amd64
Date: Wed Dec 26 18:39:18 2012
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 126
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
SourcePackage: samba4
Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 126
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Matias Fernandez (matiasefernandez) wrote on 2012-12-26:

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 (353 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (53.3 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (124.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (1.3 KiB, application/x-gzip)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-12-27:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in samba4 (Ubuntu):
status:	New → Confirmed

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2013-01-01:

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.