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
Bug occurs after first boot with natty live-usb just after installing Broadcom STA wireless drivers. These apparently install ok (as I'm able to access the internet). I'm not sure this affects the usability of the system, but the crash could be confusing to new users.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu6
ProcVersionSign
Uname: Linux 2.6.38-1-generic i686
NonfreeKernelMo
Architecture: i386
Date: Sun Feb 13 13:59:45 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
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: 06/16/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.58
dmi.board.name: 30CC
dmi.board.vendor: Quanta
dmi.board.version: 79.2E
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv6700 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.