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

[Tiare Balbi]

Crash in start system

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
NonfreeKernelModules: nvidia
.var.log.jockey.log:

Architecture: amd64
Date: Mon May 23 12:52:55 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64+mac (20110413)
InterpreterPath: /usr/bin/python2.7
MachineType: ECS P35T-A
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=e11eeb87-c7c7-40cc-a17e-4ec51f095b2e 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 17-18: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/23/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P35T-A
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd01/23/2008:svnECS:pnP35T-A:pvr1.0:rvnECS:rnP35T-A:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: P35T-A
dmi.product.version: 1.0
dmi.sys.vendor: ECS

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