jockey-text crashed with UnicodeEncodeError in error_msg(): 'ascii' codec can't encode character u'\xe6' in position 17: ordinal not in range(128)

[Kimr1508]

Happened after installing alpha 3 today and did an update to get the latest updates.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Wed Mar 9 22:39:52 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 5315
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 LANGUAGE=da_DK.UTF-8
 PATH=(custom, no user)
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic root=UUID=9a05e41d-824b-4cdf-82a0-efbc72e60765 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-text', '-C', '--no-dbus']
SourcePackage: jockey
Title: jockey-text crashed with UnicodeEncodeError in error_msg(): 'ascii' codec can't encode character u'\xe6' in position 17: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/10/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.45
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.45
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.45
dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5315:pvrV1.45:rvnAcer:rnAcadia:rvrV1.45:cvnAcer:ct1:cvrV1.45:
dmi.product.name: Aspire 5315
dmi.product.version: V1.45
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 #729526, 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.