jockey-gtk crashed with GError in function(): Icon 'jockey-disabled' not present in theme

[andromedar]

none

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sat Feb 12 09:28:11 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110210)
InterpreterPath: /usr/bin/python2.7
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion dv6000 (RY606EA#UUG)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 PATH=(custom, no user)
 LC_MESSAGES=en_AG.utf8
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8:en
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-3-generic root=UUID=67bdc94a-08e2-4505-8c43-74eca3ecc046 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with GError in function(): Icon 'jockey-disabled' not present in theme
UserGroups:

dmi.bios.date: 03/09/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.42
dmi.board.name: 30B8
dmi.board.vendor: Quanta
dmi.board.version: 65.2C
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.42:bd03/09/2009:svnHewlett-Packard:pnHPPaviliondv6000(RY606EA#UUG):pvrRev1:rvnQuanta:rn30B8:rvr65.2C:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6000 (RY606EA#UUG)
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

[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 #715753, 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.