Ubuntu
isight-firmware-tools package

macbook 3,1, MacOS 10.6.2, package isight-firmware-tools 1.4.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

Bug #548861 reported by Naoyuki Tai on 2010-03-26

This bug report is a duplicate of: Bug #420834: package isight-firmware-tools 1.2-8 failed to install/upgrade: subprocess post-installation script returned error exit status 134. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	isight-firmware-tools (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: isight-firmware-tools

MacBook 3,1, MacOS 10.6.2, Fresh Ubuntu Karmic Installation.

ProblemType: Package
AptOrdering:
isight-firmware-tools: Install
isight-firmware-tools: Configure
Architecture: i386
Date: Fri Mar 26 10:27:50 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 134
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: isight-firmware-tools 1.4.2-1
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: isight-firmware-tools
Title: package isight-firmware-tools 1.4.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

Naoyuki Tai (ntai) wrote on 2010-03-26:

Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (57.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (30.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-03-28:

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 420834, 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. Please continue to report any other bugs you may find.