jockey-gtk crashed with ImportError in <module>()

[Sziráki Tamás]

First time i had crash "pybootchartgui crashed with ImportError in <module>()" written in bug#518326, then crash "apport-gtk crashed with ImportError in <module>()" written in bug#603919, then this crash.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: jockey-gtk 0.5.8-0ubuntu8.1
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic i686
Architecture: i386
Date: Sun Jul 11 21:19:40 2010
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100626)
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 Device 002: ID 80ee:0021
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-7-generic root=/dev/sda6 ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANG=hu_HU.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/pymodules/python2.6/gtk-2.0/gi/__init__.py", line 27, in <module>
     from gi.repository import GObject
 ImportError: cannot import name GObject
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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