jockey-gtk crashed with UnicodeEncodeError in update_tree_model(): '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
when i ask to enable the extra graphics mode
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
CurrentDmesg:
[ 17.554179] r8169 0000:02:00.0: eth0: link up
[ 17.554439] ADDRCONF(
[ 18.906127] EXT4-fs (sda5): re-mounted. Opts: errors=
[ 27.016392] EXT4-fs (sda5): re-mounted. Opts: errors=
[ 27.760019] eth0: no IPv6 routers present
Date: Sun Jan 30 19:11:36 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu-Studio 11.04 "Natty Narwhal" - Alpha i386 (20101130)
InterpreterPath: /usr/bin/python2.7
MachineType: System manufacturer System Product Name
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
LANGUAGE=
LANG=el_GR.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 audio cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/26/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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.