jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()

[[e-mail]]

same as another bug, except this happened in i686 version of 10.10 LiveCD during installation.

I've been having tons of problems getting any of the recent distro LiveCDs to install; this includes Kubuntu 10.10, Ubuntu 10.10 and Ubuntu 10.04 LTS. Mostly this is because of another bug, which I will report later.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: jockey-gtk 0.5.10-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Thu Apr 7 02:50:35 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: HP-Pavilion NP200AAR-ABA a6720y
PackageArchitecture: all
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/25/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.21
dmi.board.name: VIOLET
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 3.02
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.21:bd03/25/2010:svnHP-Pavilion:pnNP200AAR-ABAa6720y:pvr:rvnPEGATRONCORPORATION:rnVIOLET:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: NP200AAR-ABA a6720y
dmi.sys.vendor: HP-Pavilion

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