jockey-gtk crashed with UnicodeEncodeError in update_tree_model(): 'ascii' codec can't encode character u'\u0159' in position 4: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu natty (development branch)
11.04
2.6.38-1-generic
Package: jockey (0.8-0ubuntu4) natty;
Crashed when looking for additional drivers for my Radeon graphics card. I was trying to use a switcheroo script before that (to turn off my Radeon and use an integrated Intel graphics card) to reduce power consumption.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.8-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Sat Jan 29 11:08:06 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
MachineType: Acer Aspire 5810TZG
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
LANGUAGE=
LANG=cs_CZ.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 nopasswdlogin plugdev sambashare
dmi.bios.date: 04/13/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.35
dmi.board.
dmi.board.name: Aspire 5810TZG
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Aspire 5810TZG
dmi.product.
dmi.sys.vendor: Acer
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.