Ubuntu
halevt package

package halevt 0.1.6.2-1.3 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 100

Bug #790311 reported by xam85it on 2011-05-30

This bug report is a duplicate of: Bug #746949: package halevt 0.1.6.2-1.3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 100. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: halevt

impossible to upgrade xubuntu 11.04

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: halevt 0.1.6.2-1.3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri May 13 22:31:55 2011
ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 100
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
SourcePackage: halevt
Title: package halevt 0.1.6.2-1.3 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 100
UpgradeStatus: Upgraded to natty on 2011-04-30 (29 days ago)

Tags:

Revision history for this message

xam85it (xam8re) wrote on 2011-05-30:

AptOrdering.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (382 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (53.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (1.1 KiB, application/x-gzip)

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-31:

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