jockey-text crashed with UnicodeEncodeError in write(): '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
next to de login
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-common 0.9.2-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
.var.log.
Architecture: i386
CurrentDmesg:
[ 26.114862] EXT4-fs (sda7): re-mounted. Opts: commit=0
[ 26.944007] eth0: no IPv6 routers present
Date: Mon Apr 25 15:07:02 2011
ExecutablePath: /usr/bin/
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Beta i386 (20110418)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=pt_BR.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 17-18: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 10/16/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.
dmi.board.name: M2N68-AM SE2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
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 #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.