Ubuntu
samba4 package

package samba4 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1

Bug #771461 reported by pascale90 on 2011-04-26

This bug report is a duplicate of: Bug #728840: upgradeprovision crashed with LdbError in connect(): (80, 'Failed to load modules from: /usr/lib/samba/ldb\n'). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: samba4

questo errore si è verificato nel passaggio dalla 10.10 alla 11.04

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: samba4 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
AptOrdering:
fusion-icon: Install
samba4: Configure
fusion-icon: Configure
Architecture: i386
Date: Tue Apr 26 22:14:45 2011
ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: samba4
Title: package samba4 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
UpgradeStatus: Upgraded to natty on 2011-04-26 (0 days ago)

Tags:

Revision history for this message

pascale90 (pascale90) wrote on 2011-04-26:

Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Df.txt Edit (457 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (50.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (5.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-04-27:

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