Ubuntu
halevt package

package halevt 0.1.6.2-1.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 100

Bug #859661 reported by Hector Dufau on 2011-09-26

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

HP G42-440BR Notebook PC
Ubuntu 11

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: halevt 0.1.6.2-1.3
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Mon Sep 26 10:49:07 2011
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 100
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: halevt
Title: package halevt 0.1.6.2-1.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 100
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Hector Dufau (contato-hectordufau) wrote on 2011-09-26:

AptOrdering.txt Edit (209 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (50.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-09-26:

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.