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

[anm1]

xUbuntu 11.04 beta2 at first start after installation in virtualbox

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
Architecture: i386
CurrentDmesg:
 [ 20.880070] eth0: no IPv6 routers present
 [ 29.157211] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
Date: Thu Apr 14 23:21:06 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413.2)
InterpreterPath: /usr/bin/python2.7
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
 LANGUAGE=ru_RU.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=a3856556-2811-409d-bc45-d0de41c50047 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: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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