jockey-gtk crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'ICON_LOOKUP_USE_BUILTIN'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Put daily build on USB on Jan 29 2011. Boot it up to try it. Tried installing nvidia drivers, moved over sized window around to select recommended driver and activate it. Then a crash report opened.
Description: Ubuntu natty (development branch)
Release: 11.04
jockey-gtk:
Installed: 0.8-0ubuntu4
Candidate: 0.8-0ubuntu4
Version table:
*** 0.8-0ubuntu4 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Sun Jan 30 20:13:31 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110130)
MachineType: Dell Inc. XPS M1330
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'ICON_LOOKUP_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/08/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0U8042
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.
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.