jockey-gtk crashes on launch via indicator

[Piet]

i want to install ATI restricted drivers trough jockey but i can't

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic-pae 2.6.38-rc4
Uname: Linux 2.6.38-3-generic-pae i686
Architecture: i386
Date: Tue Feb 15 10:47:54 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110212)
InterpreterPath: /usr/bin/python2.7
MachineType: System manufacturer System Product Name
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-3-generic-pae root=UUID=49eaca9c-5e3c-49cf-9589-71a0eaab7cff ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with GError in function(): Icon 'jockey-disabled' not present in theme
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/02/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-AM EPU
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd07/02/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[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.