Bug 783833 - [abrt] autojump-19-2.fc16: utf_8.py:16:decode:UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 68: invalid continuation byte
Summary: [abrt] autojump-19-2.fc16: utf_8.py:16:decode:UnicodeDecodeError: 'utf8' code...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: autojump
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thibault North
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:86c0bb7b5b44f1c3b9dbe427618...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-22 16:50 UTC by Vesa Halttunen
Modified: 2013-02-14 02:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 02:27:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vesa Halttunen 2012-01-22 16:50:50 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        python /usr/bin/autojump -a '/media/f217cada-c236-44a7-850c-51ee16003a3a/Backup/Vesuri/Pictures/j\xe4te'
comment:        I changed the current directory (with cd) to a directory that had its name encoded in ISO-8859-15 while the current locale was UTF-8. The directory name had the character ä in it (0xe4 in ISO-8859-1).
executable:     /usr/bin/autojump
kernel:         3.1.9-1.fc16.i686.PAE
reason:         utf_8.py:16:decode:UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 68: invalid continuation byte
time:           Sat 21 Jan 2012 09:09:51 PM EET
uid:            1000
username:       vesuri

backtrace:
:utf_8.py:16:decode:UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 68: invalid continuation byte
:
:Traceback (most recent call last):
:  File "/usr/bin/autojump", line 314, in <module>
:    success=shell_utility()
:  File "/usr/bin/autojump", line 226, in shell_utility
:    dicadd(path_dict, decode(args[-1]))
:  File "/usr/bin/autojump", line 69, in decode
:    return text.decode(encoding,errors)
:  File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
:    return codecs.utf_8_decode(input, errors, True)
:UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 68: invalid continuation byte
:
:Local variables in innermost frame:
:input: '/media/f217cada-c236-44a7-850c-51ee16003a3a/Backup/Vesuri/Pictures/j\xe4te'
:errors: 'strict'

Comment 1 Thibault North 2012-01-29 22:33:40 UTC
Issue posted upstream.

Comment 2 William Ting 2012-03-15 22:11:46 UTC
Hi Vesu,

I was unable to reproduce your bug locally. I checked out and installed release v16 (--version option wasn't added until later).

	[ting@noa ~]$ locale | grep LANG
	LANG=en_US.utf8
	[ting@noa ~]$ which autojump
	/usr/bin/autojump
	[ting@noa ~]$ autojump --version
	Unknown command line argument: option --version not recognized
	[ting@noa ~]$ cd /media/f217cada-c236-44a7-850c-51ee16003a3a/Backup/Vesuri/Pictures/jäte/
	[ting@noa jäte]$ pwd
	/media/f217cada-c236-44a7-850c-51ee16003a3a/Backup/Vesuri/Pictures/jäte
	[ting@noa jäte]$ 

What filesystem was the mounted media?

Comment 3 Vesa Halttunen 2012-04-03 13:02:45 UTC
(In reply to comment #2)
> What filesystem was the mounted media?

ext2.

Comment 4 Vesa Halttunen 2012-04-03 13:04:37 UTC
The point is that the directory name contains the ISO-8859-15 character ä (0xe4) because the directory was created when the system locale was ISO-8859-15. Now that the system locale is UTF-8 the directory name could not be parsed.

Comment 5 Thibault North 2012-12-12 17:24:24 UTC
Vesa, have the new releases of autojump fixed your problem ?

Comment 6 Fedora End Of Life 2013-01-17 00:34:28 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Fedora End Of Life 2013-02-14 02:27:16 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.