jockey-gtk crashed with UnicodeEncodeError in update_tree_model(): 'ascii' codec can't encode characters in position 8-10: ordinal not in range(128)

[linchao]

No further information

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Date: Wed Feb 2 12:49:59 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110131)
InterpreterPath: /usr/bin/python2.7
MachineType: Dell Inc. Inspiron N5010
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
 LANGUAGE=zh_CN:zh:en_GB:en
 LANG=zh_CN.UTF-8
 LC_MESSAGES=zh_CN.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-1-generic root=UUID=799afab1-c9d7-415b-b013-49dc07e17e77 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with UnicodeEncodeError in update_tree_model(): 'ascii' codec can't encode characters in position 8-10: ordinal not in range(128)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/17/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0YXXJJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/17/2010:svnDellInc.:pnInspironN5010:pvrA10:rvnDellInc.:rn0YXXJJ:rvrA10:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Inspiron N5010
dmi.product.version: A10
dmi.sys.vendor: Dell 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 #706607, 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.