jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()

[linker7474]

I was installing nvidia drivers (current & 173 afterwards) unsucessfully both of them.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: jockey-gtk 0.5.8-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
CheckboxSubmission: 7f4bbd8494c26929497a8a9b78c447e0
CheckboxSystem: c9408cd3c162025ca40129a452c91edc
Date: Sun Apr 4 00:55:23 2010
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100329)
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 045e:0084 Microsoft Corp. Basic Optical Mouse
 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
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=d38ae100-6664-45b6-8e54-90565c7686da ro quiet splash
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANG=es_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/04/2006
dmi.bios.vendor: Intel Corp.
dmi.bios.version: VA84510A.86A.0056.P20.0605040337
dmi.board.name: D845GLVA
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC30423-202
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrVA84510A.86A.0056.P20.0605040337:bd05/04/2006:svn:pn:pvr:rvnIntelCorporation:rnD845GLVA:rvrAAC30423-202:cvn:ct2:cvr:

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