jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode character u'\xfa' in position 11: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
on ubuntu 11.10
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Sun Jul 31 11:29:21 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110731)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS 00000000000000000
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=es_ES.UTF-8
LANGUAGE=
LC_COLLATE=C
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode character u'\xfa' in position 11: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 03/08/2006
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.01
dmi.board.name: 10AD
dmi.board.vendor: FUJITSU
dmi.board.version: 3B11
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.
dmi.modalias: dmi:bvnPhoenix:
dmi.product.name: 00000000000000000
dmi.product.
dmi.sys.vendor: FUJITSU SIEMENS
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.