jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions().

[itvrd]

 This error appear next: After boot a LiveCD i setup wireless network. After this, i run installer and it ask me about network and in this moment error is appear.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CasperVersion: 1.284
Date: Thu Sep 29 07:40:00 2011
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
MachineType: Quanta TWH
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz
PythonArgs: ['/usr/bin/jockey-gtk', '--check']
SourcePackage: jockey
Title: jockey-gtk crashed with BackendCrashError in convert_dbus_exceptions()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/03/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: DR192
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: TWH
dmi.board.vendor: Quanta
dmi.board.version: TBD
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: US
dmi.modalias: dmi:bvnINSYDE:bvrDR192:bd03/03/2011:svnQuanta:pnTWH:pvr04:rvnQuanta:rnTWH:rvrTBD:cvnQuanta:ct10:cvrUS:
dmi.product.name: TWH
dmi.product.version: 04
dmi.sys.vendor: Quanta

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