bcm43xx-fwcutter required by restricted-manager, but isn't included

bcm43xx-fwcutter package is in universe and not shipped with the livecd, this is the cause of the bug.

r-m should check if the needed repo is enabled and in case inform the user

I'm actually having this same problem. I installed via the text-only disc, ran "sudo apt-get update", then "sudo apt-get install bcm43xx-fwcutter". After retrieving and unpacking the package, here's what it spit back at me:

Setting up bcm43xx-fwcutter (1:006-1) ...
--05:40:37-- http://boredklink.googlepages.com/wl_apsta.o
           => `wl_apsta.o'
Resolving boredklink.googlepages.com... 72.14.203.118
Connecting to boredklink.googlepages.com|72.14.203.118|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 756 [text/html]

100%[===================================>] 756 --.--K/s

05:40:37 (41.62 MB/s) - `wl_apsta.o' saved [756/756]

Sorry, the input file is either wrong or not supported by bcm43xx-fwcutter.
This file has an unknown MD5sum a58843b5ee79d015adf8c54178186487.
dpkg: error processing bcm43xx-fwcutter (--configure):
 subprocess post-installation script returned error exit status 255
Errors were encountered while processing:
 bcm43xx-fwcutter
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

I reinstalled Feisty, got the same error message, completely removed bcm43xx-fwcutter (and the firmware file it placed in /tmp) and then installed the package again and it went through fine. (I've since reinstalled Gutsy) So it appears the place the script is getting the firmware from isn't all that reliable, perhaps?

Fixed in bzr head.

restricted-manager (0.24) gutsy; urgency=low

  [ Matteo Zandi ]
  * RestrictedManager/lrm_driver.py: load_lrmc_disabled() and
    save_lrmc_disabled() now handle trailing spaces in
    /etc/default/linux-restricted-modules-common. (LP: #122359)
  * RestrictedManager/bcm43xx.py: remove fake firmware file when
    disabling bcm43xx.
  * restricted-manager: Added new class DefaultHandlerMessageDialog that can be
    used to give messages from handlers.

  [ Martin Pitt ]
  * debian/restricted-manager.postinst: Do not call addgroup if the admin
    group already exists. In some corner cases, addgroup fails at this
    condidion. (LP: #122892)
  * Add man/restricted-manager.8: man page for r-m, thanks to Cesare
    Tirabassi! (LP: #128697)
  * restricted-manager: Check for l-r-m-generic package instead of the kernel
    ABI specific one. (LP: #107705)
  * debian/control: Add dependency to l-r-m-{generic,i386} on i386/amd64, since
    r-m does not work without it anyway and it just creates confusion.
  * RestrictedManager/bcm43xx.py: Check if bcm43xx-fwcutter could actually get
    installed before proceeding.
  * RestrictedManager/core.py, install_package(): Check that package is
    actually available; if not, point out that the software source for this
    needs to be enabled. Based on original patch of Matteo, but simplified and
    robustified. (LP: #123061, LP: #124304)

 -- Martin Pitt <email address hidden> Wed, 01 Aug 2007 12:20:55 +0200

For me, the issue seems to be the script is looking to use the wl_apsta.o file from googlepages. If you try and get this file directly - it seems the site is over its bandwidth limit. This would explain why the script fails. Either pay for more bandwidth - or setup a new host location for the file.

Alex

I tried downloading wl_apsta.o first
then i chose "use a local file" but the browse button doesn't work
i introduced location by hand but now the ok button doesn't work

i can't load the firmware using the gui

Notes: gutsy tribe cd 4, all updates applied