jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()

[solariiknight]

random crash. was doing nothing

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
CurrentDmesg:
 [ 17.356244] lp: driver loaded but no devices found
 [ 17.430018] ppdev: user-space parallel port driver
 [ 26.048009] eth0: no IPv6 routers present
Date: Fri Oct 28 05:21:40 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: System manufacturer System Product Name
PackageArchitecture: all
ProcCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
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: 01/15/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0507
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-AM IN
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0507:bd01/15/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMIN:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[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.