jockey-kde crashed with TypeError: expected 1 arguments, got 0

[rolmops]

jockey-kde crashed with TypeError: expected 1 arguments, got 0

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-kde 0.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Sun Jul 31 00:20:18 2011
ExecutablePath: /usr/bin/jockey-kde
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110727)
InterpreterPath: /usr/bin/python2.7
MachineType: ASUSTeK Computer Inc. G2S
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic root=UUID=18b27c13-88d3-4960-98bc-b153f42c8554 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-kde']
SourcePackage: jockey
Title: jockey-kde crashed with TypeError: expected 1 arguments, got 0
Traceback: TypeError: expected 1 arguments, got 0
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/31/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G2S
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.:bvr300:bd12/31/2007:svnASUSTeKComputerInc.:pnG2S:pvr1.0:rvnASUSTeKComputerInc.:rnG2S:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G2S
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 #820777, 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.