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

[Konstantinos Kalyvas]

crashes in random moments

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 i686
Architecture: i386
Date: Tue Apr 26 17:12:47 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer AO531h
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=el_GR.UTF-8
 SHELL=/bin/bash
 LANGUAGE=el_GR.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=6a087b98-118c-403e-a0d5-46b9db196e1c 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: 08/25/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3117
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3117:bd08/25/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer

[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.