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

[Sherhan]

Problem

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
.var.log.jockey.log:

Architecture: i386
Date: Sun Apr 17 22:17:47 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HP ProBook 4510s
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 LANGUAGE=ru_RU.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=ce93dd54-70b9-43fc-88d3-86332e5b28d3 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-text', '-C', '--no-dbus']
SourcePackage: jockey
Title: jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/23/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZI Ver. F.15
dmi.board.name: 3074
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 24.0E
dmi.chassis.asset.tag: CNU0131829
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.15:bd02/23/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.15:rvnHewlett-Packard:rn3074:rvrKBCVersion24.0E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4510s
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard

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