Ubuntu
samba4 package

package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 126 zurück

Bug #1046552 reported by Matthias Andree on 2012-09-05

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

This is with leftover configuration from a previous samba3 install.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Wed Sep 5 23:01:41 2012
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 126 zurück
SourcePackage: samba4
Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 126 zurück
UpgradeStatus: Upgraded to precise on 2012-05-13 (115 days ago)

Tags:

Revision history for this message

Matthias Andree (matthias-andree) wrote on 2012-09-05:

AptOrdering.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (887 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (245.6 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (2.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (8.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2012-09-05:

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.