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

[[e-mail]]

No.

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
Date: Mon Apr 18 05:56:21 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
MachineType: VIA VN800
PackageArchitecture: all
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
 LANGUAGE=hu_HU.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=d7917fa4-b6bb-4630-ab79-2f142134734a ro quiet noapic 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'\xe9' in position 4: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/27/2006
dmi.bios.vendor: Phoenix
dmi.bios.version: 2004 Q1
dmi.board.name: VN800
dmi.board.vendor: VIA
dmi.board.version: VT6297A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr2004Q1:bd09/27/2006:svnVIA:pnVN800:pvrVT6297A:rvnVIA:rnVN800:rvrVT6297A:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VN800
dmi.product.version: VT6297A
dmi.sys.vendor: VIA

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