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

[Nicolas Valcarcel]

in gnome3 "system settings", clicked on "hardware" and got apport reporting this.

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

Architecture: amd64
Date: Thu Aug 25 10:39:59 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
MachineType: Dell Inc. Studio 1458
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=7589fa4d-307c-44de-81cb-0a01e2723e4b 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.112 was not provided by any .service files
UpgradeStatus: Upgraded to oneiric on 2011-08-25 (0 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sbuild
dmi.bios.date: 07/27/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0133D9
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/27/2010:svnDellInc.:pnStudio1458:pvrA06:rvnDellInc.:rn0133D9:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Studio 1458
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

[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.