jockey-text crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
In the latest updated oneiric jockey(-text and -gtk) of version 0.9.4-0ubuntu2 (jockey-common) exits with the following error without showing any window:
ERROR:dbus.
Traceback (most recent call last):
File "/usr/bin/
sys.
File "/usr/lib/
self.
File "/usr/bin/
self.
File "/usr/bin/
for h_id in self.get_
File "/usr/lib/
return self.backend(
File "/usr/lib/
self.
File "/usr/lib/
if self._dbus_
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.4-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-9-generic x86_64
.var.log.
Architecture: amd64
Date: Wed Aug 24 09:49:18 2011
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-text crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.04
dmi.board.
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 83.15
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.