jockey-gtk crashed with DBusException in call_blocking()

[Removed by request]

this happened immediately after booting up when the desktop appeared. (Xubuntu 10.04 Beta1 i386)

ProblemType: Crash
.var.log.jockey.log:

Architecture: i386
Date: Tue Mar 23 00:26:45 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: HP Pavilion 04 P7519A-ABA 551W
Package: jockey-gtk 0.5.8-0ubuntu1
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xhostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/22/2002
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: 3.07
dmi.board.name: P4S-LA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvr3.07:bd05/22/2002:svnHPPavilion04:pnP7519A-ABA551W:pvr20000WM101MISSO:rvnASUSTeKComputerINC.:rnP4S-LA:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
dmi.product.name: P7519A-ABA 551W
dmi.product.version: 20000WM101MISSO
dmi.sys.vendor: HP Pavilion 04

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