Ubuntu
samba package

package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

Bug #838309 reported by Rodox12 on 2011-08-31

This bug report is a duplicate of: Bug #791944: [SRU] package samba 2:3.5.8~dfsg-1ubuntu2.2 failed to install/upgrade: broken permissions/configuration cause daemons not to start correctly. Edit Remove

This bug affects 1 person

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

Bug Description

it was upgrading when it crashed

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: samba 2:3.5.8~dfsg-1ubuntu2.3
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Wed Aug 31 15:52:13 2011
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
RelatedPackageVersions:
nautilus 1:2.32.2.2-0ubuntu3~ppa170
gvfs 1.8.0-0ubuntu3
SambaClientRegression: Yes
SourcePackage: samba
Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Rodox12 (rodox12) wrote on 2011-08-31:

AptOrdering.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (44.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (4.9 KiB, text/plain; charset="utf-8")
SambaInstalledVersions.txt Edit (389 bytes, text/plain; charset="utf-8")

Revision history for this message

James Page (james-page) wrote on 2011-09-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 791944, 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.