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

[SoftLibre]

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

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 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
Date: Mon Aug 29 15:47:02 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
MachineType: Phoenix Technologies RS780+SB700
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=86ce9257-f3ba-4027-9268-f93fdfd49420 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.70 was not provided by any .service files
UpgradeStatus: Upgraded to oneiric on 2011-08-23 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/09/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: LP JR 790GX-M3H5
dmi.board.vendor: DFI Inc.
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Phoenix Technologies
dmi.chassis.version: RS780+SB700
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/09/2009:svnPhoenixTechnologies:pnRS780+SB700:pvr12345678:rvnDFIInc.:rnLPJR790GX-M3H5:rvr1.0:cvnPhoenixTechnologies:ct3:cvrRS780+SB700:
dmi.product.name: RS780+SB700
dmi.product.version: 12345678
dmi.sys.vendor: Phoenix Technologies

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