jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-5: ordinal not in range(128)

[[e-mail]]

this issue was found during trying Ubuntu live DVD for further information about additional diver.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sat Apr 30 10:10:09 2011
ExecutablePath: /usr/bin/jockey-text
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
MachineType: LENOVO 44013XV
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -a
ProcEnviron:
 LANGUAGE=zh_TW
 LC_COLLATE=C
 PATH=(custom, no user)
 LANG=zh_TW
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=zh_TW keyboard-configuration/layoutcode?=us
PythonArgs: ['/usr/bin/jockey-text', '-a']
SourcePackage: jockey
Title: jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-5: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8JET23WW (1.05 )
dmi.board.asset.tag: Not Available
dmi.board.name: 44013XV
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:bvr8JET23WW(1.05):bd02/22/2011:svnLENOVO:pn44013XV:pvrThinkPadEdgeE420s:rvnLENOVO:rn44013XV:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 44013XV
dmi.product.version: ThinkPad Edge E420s
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 #749854, 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.