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

[Qusai Abu Hilal]

I open additional drivers and it crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
.var.log.jockey.log:

Architecture: amd64
Date: Wed Aug 24 16:18:12 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 4930
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=b728b672-7ad5-4457-81bb-cd706131f693 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.47 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: 07/22/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 4930
dmi.board.vendor: Acer
dmi.board.version: V1.22
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.22
dmi.modalias: dmi:bvnAcer:bvrV1.22:bd07/22/2010:svnAcer:pnAspire4930:pvrV1.22:rvnAcer:rnAspire4930:rvrV1.22:cvnAcer:ct1:cvrV1.22:
dmi.product.name: Aspire 4930
dmi.product.version: V1.22
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.