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

[ken farmer]

trying to install the nvidia restricted driver for my laptop (geforce m7600)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Sep 30 03:26:26 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
MachineType: TOSHIBA ��������������������������������
PackageArchitecture: all
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=ae4dcf5f-057d-4f9e-87ca-e54fde9ecbf7 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with GError in function(): Icon 'gtk-refresh' not present in theme
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/19/20092
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V4.70
dmi.board.name: ��������������������������������
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd01/19/20092:svnTOSHIBA:pn:pvr:rvnTOSHIBA:rn:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: ��������������������������������
dmi.product.version: ��������������������������������
dmi.sys.vendor: TOSHIBA

[ken farmer (asaone1)]

trying to install the nvidia restricted driver for ny laptop (grforce m7600)

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