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

[Britt Yazel]

happened when trying to access jockey

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: Sat Aug 27 00:54:26 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 5553
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=32bb4dc3-9bf4-44dc-af1d-05050ece7830 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.720 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: 04/25/2011
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.23
dmi.board.name: JV51_DN
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:bvnPhoenixTechnologiesLTD:bvrV1.23:bd04/25/2011:svnAcer:pnAspire5553:pvrNotApplicable:rvnAcer:rnJV51_DN:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5553
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 #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.