apturl-gtk crashed with UnicodeDecodeError in parseArgs(): 'ascii' codec can't decode byte 0xe3 in position 18: ordinal not in range(128)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apturl (Ubuntu) |
Fix Released
|
Medium
|
Canonical Foundations Team | ||
Precise |
Fix Released
|
Medium
|
Canonical Foundations Team |
Bug Description
TEST CASE:
0. Install a non-english locale like fr or ja
1. In a terminal run the following command:
$ LANG=fr_FR.utf8 apturl-gtk azertyuiop
EXPECTED RESULT:
A dialog pops up displaying a localized error message "Invalid url: 'azertyuiop' given, exiting"
ACTUAL RESULT:
It crashes with the trace below:
-----
Traceback (most recent call last):
File "/usr/bin/
sys.
File "/usr/lib/
apturl_list = self.parseArgs()
File "/usr/lib/
"%s" % str(e))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 7-8: ordinal not in range(128)
-----
=== Original Description ===
I don't know
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apturl 0.5.1ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-7-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Tue Jan 3 18:50:46 2012
ExecutablePath: /usr/bin/apturl-gtk
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/apturl-gtk /home/username/
ProcEnviron:
PATH=(custom, no user)
LANG=ja_JP.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: apturl
Title: apturl-gtk crashed with UnicodeDecodeError in parseArgs(): 'ascii' codec can't decode byte 0xe3 in position 18: ordinal not in range(128)
UpgradeStatus: Upgraded to precise on 2012-01-02 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
tags: | removed: need-duplicate-check |
Changed in apturl (Ubuntu Precise): | |
importance: | High → Medium |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.