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

[Hernan.]

jockey

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
.var.log.jockey.log:

Architecture: i386
Date: Tue Aug 23 13:42:31 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
InterpreterPath: /usr/bin/python2.7
MachineType: FOXCONN G43M01
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -l
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=es_VE:es
 LC_MESSAGES=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=7dd239ef-a04a-4b87-bb27-397baa645b07 ro single nomodeset
PythonArgs: ['/usr/bin/jockey-text', '-l']
SourcePackage: jockey
Title: jockey-text crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.120 was not provided by any .service files
UpgradeStatus: Upgraded to oneiric on 2011-08-23 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/24/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G43M01
dmi.board.vendor: FOXCONN
dmi.board.version: 1.1
dmi.chassis.type: 6
dmi.chassis.vendor: Foxconn
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd07/24/2008:svnFOXCONN:pnG43M01:pvr1.1:rvnFOXCONN:rnG43M01:rvr1.1:cvnFoxconn:ct6:cvr:
dmi.product.name: G43M01
dmi.product.version: 1.1
dmi.sys.vendor: FOXCONN

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