jockey-gtk crashed with GError in function(): Symbol »jockey-disabled« nicht im Thema vorhanden

[Stefan Kriwanek (Divan)]

After initial install I started a "Gnome Classic" session and clicked on "activate drivers" after the balloon notifying of "restricted drivers available" popped up.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
CurrentDmesg: [ 46.754641] hda-intel: IRQ timing workaround is activated for card #2. Suggest a bigger bdl_pos_adj.
Date: Wed Feb 9 22:35:35 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
MachineType: ASUSTeK Computer INC. N5051Tp
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.UTF-8
 LC_MESSAGES=de_DE.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-generic root=UUID=d7cf5a82-a51d-499b-b3e1-e8644baffe2a ro
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with GError in function(): Symbol »jockey-disabled« nicht im Thema vorhanden
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 225
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: N5051Tp
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr225:bd05/27/2009:svnASUSTeKComputerINC.:pnN5051Tp:pvr1.0:rvnASUSTeKComputerINC.:rnN5051Tp:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: N5051Tp
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #715925, so 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.