Bug 1204428 - coredump when command line contains LANG=en_US umlaut (latin1 encoding)
Summary: coredump when command line contains LANG=en_US umlaut (latin1 encoding)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: Thunar
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-21 23:53 UTC by Peter Backes
Modified: 2015-12-02 17:44 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 10:22:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Xfce 11814 0 None None None Never

Description Peter Backes 2015-03-21 23:53:45 UTC
Description of problem:
running thunar with an umlaut as the parameter causes it to instantly dump core

Version-Release number of selected component (if applicable):
Thunar-1.6.4-1.fc21.i686

How reproducible:
always

Steps to Reproduce:
1. /usr/bin/thunar ä

Actual results:
[1]    15772 abort (core dumped)  /usr/bin/thunar ä

Expected results:
Failed to open "ä". etc.

Additional info:
I have LANG=en_US, and so a latin1 encoded 'ä' is passed to thunar. Interestingly, if you pass a UTF-8 'ä', despite LANG=en_US, it will not crash, and even output the expected result! Anyway, it should not core dump, regardless of what the command line and the locale is.

It does not have to be an umlaut, same result, for example, for ß or è. Any non-ascii char?

Comment 1 Kevin Fenzi 2015-03-22 18:36:07 UTC
I can't seem to duplicate this here with 1.6.6...

Can you try this scratch build and see if you can still see it?

https://koji.fedoraproject.org/koji/taskinfo?taskID=9297399

Comment 2 Peter Backes 2015-04-10 00:06:21 UTC
Can still reproduce it with 1.6.6

Are you sure you reproduced it correctly? You need to pass a latin1 umlaut, not a UTF8 umlaut.

Try:

/usr/bin/Thunar "`printf '\374'`"

Comment 3 Kevin Fenzi 2015-04-10 16:27:10 UTC
I could have sworn I used the right one, but yes, now I do see it. ;( 

Would you care to report this upstream? Or would you prefer I do so?

Comment 4 Fedora End Of Life 2015-11-04 15:36:44 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 5 Fedora End Of Life 2015-12-02 10:22:30 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.