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

[maxime]

Jockey don't launch

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

Architecture: i386
Date: Sat Aug 27 20:38:44 2011
ExecutablePath: /usr/bin/jockey-kde
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 3810T
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic-pae root=UUID=135df2d7-dcbf-4dd9-956d-76a5d9fc408d 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.59 was not provided by any .service files
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 08/10/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.28
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 3810T
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: dmi:bvnAcer:bvrV1.28:bd08/10/2010:svnAcer:pnAspire3810T:pvrV1.28:rvnAcer:rnAspire3810T:rvrPSMBOU-1234567:cvnAcer:ct10:cvrNone:
dmi.product.name: Aspire 3810T
dmi.product.version: V1.28
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.