Ubuntu
b43-fwcutter package

package firmware-b43-installer 4.150.10.5-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #747877 reported by Ankur Jain on 2011-04-01

This bug report is a duplicate of: Bug #711397: package firmware-b43legacy-installer 4.178.10.4-5 failed to install/upgrade due to unsupported hardware. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	b43-fwcutter (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: b43-fwcutter

i was trying to install one suggested package for ubuntu one service in order to enable sync service.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: firmware-b43-installer 4.150.10.5-5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
AptOrdering:
desktopcouch-ubuntuone: Install
firmware-b43-installer: Configure
desktopcouch-ubuntuone: Configure
Architecture: i386
Date: Sat Apr 2 00:36:23 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: b43-fwcutter
Title: package firmware-b43-installer 4.150.10.5-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to natty on 2011-03-31 (0 days ago)

Tags:

Revision history for this message

Ankur Jain (decent-ankur) wrote on 2011-04-01:

Dependencies.txt Edit (639 bytes, text/plain; charset="utf-8")
Df.txt Edit (443 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (63.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (346 bytes, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-04-22:

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 711397, 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.