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

[Ezrah]

jockey-kde Crashed when launching Additional Drivers application. Im using Kubuntu 11.10 alpha 3

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 i686
.var.log.jockey.log:

Architecture: i386
Date: Sat Aug 27 00:50:26 2011
ExecutablePath: /usr/bin/jockey-kde
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110826)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer AOD255
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=2dd274a7-15a6-4c8a-8769-46873353f5fa 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.63 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: 01/10/2011
dmi.bios.vendor: Acer
dmi.bios.version: V3.14(DDR2)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.14(DDR2)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.14(DDR2)
dmi.modalias: dmi:bvnAcer:bvrV3.14(DDR2):bd01/10/2011:svnAcer:pnAOD255:pvrV3.14(DDR2):rvnAcer:rnJE02_PT:rvrV3.14(DDR2):cvnAcer:ct10:cvrV3.14(DDR2):
dmi.product.name: AOD255
dmi.product.version: V3.14(DDR2)
dmi.sys.vendor: Acer

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 657829, so it 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.