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

[Daan W.]

Tried to install from current oineric live image to virtualbox.
could do pretty much nothing because almost every program crashed.

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

Architecture: i386
CasperVersion: 1.279
Date: Fri Aug 26 10:31:25 2011
ExecutablePath: /usr/bin/jockey-text
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110826)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -a
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 LC_COLLATE=C
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
PythonArgs: ['/usr/bin/jockey-text', '-a']
SourcePackage: jockey
Title: jockey-text crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.73 was not provided by any .service files
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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