jockey-gtk crashed with UnicodeEncodeError in update_tree_model(): 'ascii' codec can't encode characters in position 17-18: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When i use jockey, this crash
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Sat Jan 29 03:59:39 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110127)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0cf3:1006 Atheros Communications, Inc. TP-Link TL-WN422G v2 802.11g [Atheros AR9271]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer INC. A7N8X-E
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
LANGUAGE=
LANG=pt_BR.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with UnicodeEncodeError in update_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/12/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A7N8X-E Deluxe ACPI BIOS Rev 1013
dmi.board.name: A7N8X-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 2.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufactture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: A7N8X-E
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
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 #706607, 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.