package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Matthew Lee]

While using a USB boot with a 256 MB persistence file, I tried to download and install the Broadcom restricted driver on my Dell Mini9. The driver downloaded and attempted to install. Near the end of the installation, I received the error message outlined in the error submission.

ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

ubuntu@ubuntu:~$ apt-cache policy bcmwl-kernel-source
bcmwl-kernel-source:
  Installed: 5.60.48.36+bdcom-0ubuntu5
  Candidate: 5.60.48.36+bdcom-0ubuntu5
  Version table:
 *** 5.60.48.36+bdcom-0ubuntu5 0
        500 cdrom://Ubuntu-Netbook 10.10 _Maverick Meerkat_ - Release i386 (20101007)/ maverick/restricted i386 Packages
        500 http://archive.ubuntu.com/ubuntu/ maverick/restricted i386 Packages
        100 /var/lib/dpkg/status
ubuntu@ubuntu:~$

Expected outcome:

I expected the wireless driver to be installed to the bootable USB storage space and available for subsequent "live CD" boots from the USB drive.

Actual outcome:

The driver failed to install to the USB drive when the system was running in a "live CD" mode.

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Nov 6 07:12:21 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Brian Murray (brian-murray)]

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