jockey-gtk crashed with DBusException in call_blocking()

[largos]

I don't now. Sorry may english not good, but I ony wark may computers end 1 second end error. I don't now way.

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

Architecture: i386
Date: Fri Oct 30 19:17:58 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: ASUSTeK Computer Inc. F3Sr
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- debian-installer/language=pl console-setup/layoutcode?=pl
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 LANG=pl_PL.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: 04/01/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F3Sr
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd04/01/2008:svnASUSTeKComputerInc.:pnF3Sr:pvr1.0:rvnASUSTeKComputerInc.:rnF3Sr:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: F3Sr
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[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.