jockey-gtk crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'ICON_LOOKUP_USE_BUILTIN'

[George Karavasilev]

Ubuntu 11.04 Daily Build (21.1Jan.2011) x64

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Fri Jan 21 13:07:01 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110121)
MachineType: LENOVO 20023
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 LANGUAGE=bg_BG.UTF-8:bg:en_GB:en
 LANG=bg_BG.UTF-8
 LC_MESSAGES=bg_BG.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'ICON_LOOKUP_USE_BUILTIN'
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/18/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 18CN42WW(V2.51)
dmi.board.name: NITU1
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr18CN42WW(V2.51):bd01/18/2010:svnLENOVO:pn20023:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 20023
dmi.product.version: Lenovo G550
dmi.sys.vendor: LENOVO

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