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

[Stephan Krinetzki]

Every time Ubuntu boots up, this apllication crashes.

Expected: Normal Start of GNOME
Happened: jockey-text crash
Ubuntu 11.04 Beta 2

Description: Ubuntu 11.04
Release: 11.04

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: Fri Apr 22 19:09:07 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=de_DE.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=a1eb5e3e-1552-403b-8729-dc2e7310bb96 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 character u'\xfc' in position 1: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/19/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: K7VT4A+
dmi.board.version: 1.0x
dmi.chassis.asset.tag: 00000000
dmi.chassis.type: 3
dmi.chassis.version: X.XX
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/19/2004:svn:pnK7VT4A+:pvr1.0x:rvn:rnK7VT4A+:rvr1.0x:cvn:ct3:cvrX.XX:
dmi.product.name: K7VT4A+
dmi.product.version: 1.0x

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