System hangs when I use jockey for first time to enable "wl" module

Architecture: i386
DistroRelease: Ubuntu 9.10
MachineType: Acer Aspire 2920
NonfreeKernelModules: wl
Package: jockey-kde 0.5.5-0ubuntu1
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic root=UUID=26c4e14a-f104-40ec-957c-3c1e22e29d4b ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/14/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.13
dmi.board.name: Calado
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.13:bd02/14/2008:svnAcer:pnAspire2920:pvr0100:rvnAcer:rnCalado:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 2920
dmi.product.version: 0100
dmi.sys.vendor: Acer

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: bcmwl-kernel-source 5.10.91.9+bdcom-0ubuntu4
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (process:1923): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `display != NULL' failed
 (<unknown>:1923): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
 (process:1939): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `display != NULL' failed
 (<unknown>:1939): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed

Saw this on a Dell Mini 9 as well.

I experience the same on Karmic Koala when using Jockey to install fwcutter for b43 driver.

My experience is:
I click on the hardware driver icon, a screen shows up and shows that broadcom b43 driver is not active, when I click "Activate" the list of drivers is faded, and then it just hangs.

I forgot to mention. That my description of experience is on a Kubuntu system, so the application is jockey-kde.

Anyway, now that I tried again, I tried something differently.
I click on the hardware driver icon, a screen shows up and shows that broadcom b43 driver is not active (along one other driver for softmodem). I now click forth and back between the b43 driver and softmodem driver and the description is of course updated accordingly. After doing that a couple of times, I chose b43 driver and click "activate". Now a progress bar comes up and eveything seems to work perfectly.

So the problem might be related to the situation when the user clicks "activate" directly to activate the highlighted driver (the upper most line among many) without actively choosing a specific line/driver.

Jarl

Installing bcmwl-kernel-source by package manager as like as aptitude, does not cause any problem.
Installing it by jockey, cause system crash.

I think what Jarl describes is Bug #458770, unrelated to this report (jockey hangs, not the entire system).

amichair, I think you are right, my experience is much like Bug #458770. Thanks.

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

eol reached https://wiki.ubuntu.com/Releases