jockey-text crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.57 was not provided by any .service files

[Extender]

jockey-text and jockey-gtk are both crashed and not working

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
Uname: Linux 3.1.0-0301rc3-generic x86_64
.var.log.jockey.log:

Architecture: amd64
Date: Sun Aug 28 16:28:48 2011
ExecutablePath: /usr/bin/jockey-text
InterpreterPath: /usr/bin/python2.7
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.1.0-0301rc3-generic root=UUID=6de5b4fa-8f95-4b28-a740-9ca12fc6b1c4 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-text']
SourcePackage: jockey
Title: jockey-text crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.57 was not provided by any .service files
UpgradeStatus: Upgraded to oneiric on 2011-08-27 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/14/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: P41C-DE
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd12/14/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP41C-DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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