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
the big update a few days ago broke my system so it would not load x and would just boot to a black unresponsive screen. I finally got it to boot into low-rez mode and now i am trying to re-install and activate the nvidia binary driver so i can get normal resolution back. The error happened when using the proprietary driver activation thing in system/
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu6
ProcVersionSign
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Date: Wed Feb 2 03:34:14 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
InterpreterPath: /usr/bin/python2.7
MachineType: ECS-USA GeForce6100PM-M2
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
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: 12/12/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: GeForce6100PM-M2
dmi.board.vendor: ECS-USA
dmi.board.version: 2.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS-USA
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: GeForce6100PM-M2
dmi.product.
dmi.sys.vendor: ECS-USA
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.