Hide Forgot
Description of problem: I have used "Report to Admin" button in sealert browser to create a mail template. Evolution window has been opened with the mail but all lines have been terminated with CR charater which results in that strange "box" symbol (contaning 000d) that represents unprintable characters. Version-Release number of selected component (if applicable): setroubleshoot-3.0.38-2.1.el6 How reproducible: always Steps to Reproduce: 1. read above 2. 3. Actual results: Expected results: no box symbols at the end of the line Additional info:
I am not seeing this, Do you have an example of this?
Created attachment 549213 [details] screenshot added attachment with the screenshot
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Could the problem be in evolution?
(In reply to Milos Malik from comment #13) > Could the problem be in evolution? I do not know how this works precisely, and having the raw data which are passed into the Evolution would surely help, but there was a similar bug report, with message replies, filled upstream [1]. This message processing is done in gtkhtml3. There also used to be a similar issue long time ago, composer showing some end-line markers or tabs or such, but it cured on its own after some update of either pango, or cairo, or some such library being used by the gtkhtml3 dependencies. [1] https://bugzilla.gnome.org/show_bug.cgi?id=747988
Minimal reporducer for the evolution: $ mailto:?subject=subject.&body=text.%0D%0A%2a%2a%29%20text2%0d%0a
Created attachment 1029403 [details] eds patch for evolution-data-server; After some investigation the faulty code resides in evolution-data-server. The ToHTML filter encoded the \r into the ' ' sequence, instead of keeping it as part of the \r\n line ending. It will still encode out-of-order \r as the ' ', which is correct, from my point of view.
(In reply to Milan Crha from comment #15) > Minimal reporducer for the evolution: > $ mailto:?subject=subject.&body=text.%0D%0A%2a%2a%29%20text2%0d%0a The right command is (above is missing a backslash in front of the ampersand): $ mailto:?subject=subject.\&body=text.%0D%0A%2a%2a%29%20text2%0d%0a
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0581.html