jockey-gtk crashed with DBusException in call_blocking()

[JianminX]

as system suggested

ProblemType: Crash
.var.log.jockey.log: 2009-12-08 08:40:31,609 DEBUG: _check_polkit_privilege: sender :1.60 on connection <dbus._dbus.SystemBus (system) at 0x8f2f1ac> pid 4552 is not authorized for com.ubuntu.devicedriver.info: dbus.Dictionary({}, signature=dbus.Signature('ss'))
Architecture: i386
Date: Tue Dec 8 08:40:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: LENOVO 2007IBC
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: noprompt persistent BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=zh_CN console-setup/layoutcode?=cn BOOT_IMAGE=/casper/vmlinuz
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 08/23/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETD7WW (2.17 )
dmi.board.name: 2007IBC
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr79ETD7WW(2.17):bd08/23/2007:svnLENOVO:pn2007IBC:pvrThinkPadT60:rvnLENOVO:rn2007IBC:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2007IBC
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

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