Ubuntu
util-linux package

package mount 2.17.2-3.3ubuntu4 failed to install/upgrade: подпроцесс новый сценарий pre-installation возвратил код ошибки 127

Bug #720020 reported by Stepan Martiyanov on 2011-02-16

This bug report is a duplicate of: Bug #719754: package mount 2.17.2-3.3ubuntu4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 127. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	util-linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: util-linux

I got an erron during safe-upgade on mound package update. After it I try reinstall it and got this error.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: mount 2.17.2-3.3ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
Uname: Linux 2.6.38-2-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Wed Feb 16 15:52:55 2011
ErrorMessage: подпроцесс новый сценарий pre-installation возвратил код ошибки 127
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: util-linux
Title: package mount 2.17.2-3.3ubuntu4 failed to install/upgrade: подпроцесс новый сценарий pre-installation возвратил код ошибки 127

Tags:

Revision history for this message

Stepan Martiyanov (symsym) wrote on 2011-02-16:

AptOrdering.txt Edit (10.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (789 bytes, text/plain; charset="utf-8")
Df.txt Edit (441 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (64.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-02-16:

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