Ubuntu
halevt package

package halevt 0.1.6.2-1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

Bug #825334 reported by Tony Colin on 2011-08-12

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

package halevt 0.1.6.2-1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: halevt 0.1.6.2-1.3
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Aug 12 17:32:52 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 100
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: halevt
Title: package halevt 0.1.6.2-1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
UpgradeStatus: Upgraded to natty on 2011-05-22 (81 days ago)

Tags:

Revision history for this message

Tony Colin (tony-jetnet) wrote on 2011-08-12:

AptOrdering.txt Edit (467 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (452 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (56.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-08-23:

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.