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

[stavros tsigas]

jockey-kde allways crasched i cant use it

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-kde 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Sat Aug 27 14:16:26 2011
ExecutablePath: /usr/bin/jockey-kde
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 8940G
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-9-generic root=UUID=5f0dbf3e-6d4b-47b9-9934-1f07ddbdd2ac ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-kde']
SourcePackage: jockey
Title: jockey-kde crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.84 was not provided by any .service files
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/07/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.3114
dmi.board.name: SM80-CP
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.3114:bd12/07/2009:svnAcer:pnAspire8940G:pvrNotApplicable:rvnAcer:rnSM80-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 8940G
dmi.product.version: Not Applicable
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 #831803, 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.