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
Trying Ubuntu 11.04 from a USB stick, with daily build from 1/23/2011. Trying to activate 3D driver to use Unity from Ubuntu 11.0. Then this crash occurs.
lsb_release -rd
1. Description: Ubuntu natty (development branch)
Release: 11.04
2. Trying to install only 3D driver offered to me. Then this crash occurs about 3/4 of the progress bar from the driver activation.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.37-12-generic x86_64
Architecture: amd64
Date: Sun Jan 23 15:46:44 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110123)
MachineType: HP-Pavilion KJ378AA-ABA a6430f
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: 04/15/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.11
dmi.board.name: NARRA3
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 3.02
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: KJ378AA-ABA a6430f
dmi.sys.vendor: HP-Pavilion
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.