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

[manbuzhe]

i don;t known

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
.var.log.jockey.log:

Architecture: amd64
CasperVersion: 1.279
Date: Fri Aug 26 07:49:54 2011
ExecutablePath: /usr/bin/jockey-text
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110825)
MachineType: Acer Aspire 4820TG
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -a
ProcEnviron:
 LANGUAGE=zh_CN
 LC_COLLATE=C
 PATH=(custom, no user)
 LANG=zh_CN
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=zh_CN keyboard-configuration/layoutcode?=cn
PythonArgs: ['/usr/bin/jockey-text', '-a']
SourcePackage: jockey
Title: jockey-text crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.78 was not provided by any .service files
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM41_CP
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrV1.25:bd03/16/2011:svnAcer:pnAspire4820TG:pvrV1.25:rvnAcer:rnJM41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 4820TG
dmi.product.version: V1.25
dmi.sys.vendor: Acer

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