Bug 622223

Summary: abrt eats characters outside the basic latin range when submitting to bugzilla
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: abrtAssignee: Denys Vlasenko <dvlasenk>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anton, dvlasenk, iprikryl, jmoskovc, kklic, mtoman, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: abrt-2.0.3-1.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-24 03:25:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 538278    

Description Nicolas Mailhot 2010-08-08 07:51:57 UTC
Description of problem:

As seen in bug #622222 abrt eats characters outside the basic latin range when submitting to bugzilla

That means text not written in English becomes unreadable, and it is not possible to sanely report distribution UTF-8 handling problems as abrt will eat the reproducer sequences

Version-Release number of selected component (if applicable):
abrt-1.1.10-4.fc14.x86_64
abrt-addon-ccpp-1.1.10-4.fc14.x86_64
abrt-addon-kerneloops-1.1.10-4.fc14.x86_64
abrt-addon-python-1.1.10-4.fc14.x86_64
abrt-desktop-1.1.10-4.fc14.x86_64
abrt-gui-1.1.10-4.fc14.x86_64
abrt-libs-1.1.10-4.fc14.x86_64
abrt-plugin-bugzilla-1.1.10-4.fc14.x86_64
abrt-plugin-logger-1.1.10-4.fc14.x86_64
abrt-plugin-runapp-1.1.10-4.fc14.x86_64

Comment 1 Denys Vlasenko 2010-08-17 12:36:40 UTC
(In reply to comment #0)
> Description of problem:
> 
> As seen in bug #622222 abrt eats characters outside the basic latin range when
> submitting to bugzilla

abrt eats characters outside the basic latin range - where exactly?
When you enter them in "how to reproduce" field in abrt's gui tool?
Or somewhere else?

Comment 2 Nicolas Mailhot 2010-08-17 12:53:03 UTC
In the comment and "how to reproduce"

And the command capture is strange (\xc3\xa9 instead of é)

You have various examples in bug #622222 where complémentaires is replaced by complmentaires or compl\xc3\xa9mentaires, and "font(écoliercourt)" by "font(coliercourt)"

Comment 3 Denys Vlasenko 2011-05-19 14:53:17 UTC
Found the bug.

Fixed it in git with commit f3b32f8cb94bc83ded97bec478e666be6a07bf0d.

This fixes all text fields except cmdline.

Cmdline will still look like 'compl\xc3\xa9mentaires'.

Why?

We want to be a bit more paranoid about this bit of data - that is, we want to be very sure reporter gets EXACT command line. Meaning: no hidden spaces (think how these two commands from shell:
 cmd "abc def"
 cmd abc def
can look very similar...), no hidden Unicode chars which look very similar to ASCII chars (or have zero width and are invisible), etc.

If you think we should not escape cmdline, please reopen this bug and explain why you think so.

Comment 4 Nicolas Mailhot 2011-05-25 07:11:15 UTC
Is there any way to convert this in a working command line ? Because otherwise, I fear a developper receiving an abrt report with munged cli will just ignore it

Comment 5 Fedora Update System 2011-06-21 13:45:27 UTC
abrt-2.0.3-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.3-1.fc15

Comment 6 Fedora Update System 2011-06-21 23:56:20 UTC
Package abrt-2.0.3-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.3-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/abrt-2.0.3-1.fc15
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2011-06-24 03:23:32 UTC
abrt-2.0.3-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.