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

[Shanekpiper]

fresh startup

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

Architecture: amd64
Date: Sat Aug 27 03:38:44 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 8930
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=ccb7d7c6-0e70-4763-9ff4-a92268dbbe03 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.66 was not provided by any .service files
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (0 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse rtkit sambashare video
dmi.bios.date: 12/03/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 8930
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.10:bd12/03/2008:svnAcer:pnAspire8930:pvrV1.10:rvnAcer:rnAspire8930:rvrPSMBOU-1234567:cvnAcer:ct1:cvrN/A:
dmi.product.name: Aspire 8930
dmi.product.version: V1.10
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.