jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-5: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
While trying install Ubuntu 11.04 x86_64 using an USB stick, after clicking 'Install Ubuntu 11.04' icon, an error jumped, saying 'jockey-text' error.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Fri Apr 29 14:14:51 2011
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: LENOVO 6474PQ3
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=zh_TW
LC_COLLATE=C
PATH=(custom, no user)
LANG=zh_TW
SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-5: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 03/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET85WW (3.15 )
dmi.board.name: 6474PQ3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 6474PQ3
dmi.product.
dmi.sys.vendor: LENOVO
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 #749854, 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.