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

Bug #655991 reported by Glen Robinson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
b43-fwcutter (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: b43-fwcutter

Attempted to install restricted wireless driver(s). Failed with archive bad,missing message. Got the crash notification reboot.
This was with 10.10rc netbook installed on an HP Mini 210-1010NR. When run under live USB it worked fine, wireless was enabled and my wpa access code worked on reboots. I installed to the internal disk as a dual (actually 3 if you include HP's quicktonet stuff) boot system.

I expected to be able to get wireless up by selecting restricted drivers.
I was unable to get it working. Note that I had done all of the updates available over 100BT after installing from the USB flash.
I really expected this to work since it had worked while running under the live US

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: firmware-b43-installer 4.150.10.5-4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Wed Oct 6 01:09:45 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.2)
PackageArchitecture: all
SourcePackage: b43-fwcutter
Title: package firmware-b43-installer 4.150.10.5-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Revision history for this message
Glen Robinson (glentrobfc) wrote :
Revision history for this message
Glen Robinson (glentrobfc) wrote :

Reboot this afternoon, after doing some minor tweaking to windows/mouse settings showed wireless was up and after setting wpa-2 password everything is working fine. I am not sure what fixed it, perhaps one of the updates (in the batch I did early this am) and the crash message had just hung around, or ... In any case it is working now. If you want me to do anything else, eg., reinstall, or whatever let me know.

Revision history for this message
Brian Murray (brian-murray) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.