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

[kouhei motoya]

This plobrem occured, when I start LibreOffice Writer.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Sun Apr 17 12:38:08 2011
ExecutablePath: /usr/bin/jockey-text
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
MachineType: BIOSTAR Group G41-M7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/jockey-text -C --no-dbus
ProcEnviron:
 PATH=(custom, no user)
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
 LANGUAGE=ja_JP.UTF-8
 LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=e12cecc7-8f01-45e8-9ed1-aa6b8db329e7 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-63: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/03/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G41-M7
dmi.board.vendor: BIOSTAR Group
dmi.board.version: ' '
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: ' '
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd08/03/2010:svnBIOSTARGroup:pnG41-M7:pvr'':rvnBIOSTARGroup:rnG41-M7:rvr'':cvnBIOSTARGroup:ct3:cvr'':
dmi.product.name: G41-M7
dmi.product.version: ' '
dmi.sys.vendor: BIOSTAR Group

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