jockey-text crashed with UnicodeEncodeError in write(): 'ascii' codec can't encode character u'\xe8' in position 120: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello
At the first starup of the system this appear.
The jockey's icon is present in the notify area and is working, so I can download and install experimental drivers
Thanks
Fabio
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-common 0.9.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Thu Aug 18 10:31:28 2011
ExecutablePath: /usr/bin/
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0718:0628 Imation Corp.
Bus 002 Device 002: ID 046d:c313 Logitech, Inc.
Bus 002 Device 003: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcCwd: /
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.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 character u'\xe8' in position 120: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/03/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.
dmi.board.name: K8NF4G-SATA2
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K8NF4G-SATA2
dmi.product.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 760883, so it 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.