jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
bug on startup main menu on unity panel
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CurrentDmesg:
[ 30.960024] eth0: no IPv6 routers present
[ 34.792046] EXT4-fs (sda1): re-mounted. Opts: errors=
Date: Sat Apr 23 18:07:32 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
MachineType: Micro-Star International MSI Notebook VR601
PackageArchitec
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=ru_RU.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 characters in position 0-2: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/13/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A163CIMS V1.58
dmi.board.
dmi.board.name: MS-163C
dmi.board.vendor: MSI
dmi.board.version: Ver 1.000
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MSI Notebook VR601
dmi.product.
dmi.sys.vendor: Micro-Star International
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.