jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode characters in position 0-11: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Installed NVIDIA proprietary drives, rebooted and system gets me a error message/
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
Architecture: i386
Date: Sun Apr 17 13:19:09 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 002 Device 003: ID 0a81:0101 Chesen Electronics Corp. Keyboard
Bus 002 Device 002: ID 04d9:048e Holtek Semiconductor, Inc. Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07d1:3c0a D-Link System DWA-140 RangeBooster N Adapter(rev.B2) [Ralink RT2870]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
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-11: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: N68-S
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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 #758860, 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.