Bug 13078

Summary: libreoffice shouldn't url-encode document title for email subject
Product: Mageia Reporter: Bruno Cornec <bruno>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: thierry.vignaud
Version: 4Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: libreoffice-4.1.5.3-1.mga4.src.rpm CVE:
Status comment:

Description Bruno Cornec 2014-03-23 18:21:23 CET
Description of problem:

This is a known upstream bug fixed since.
Bug at: https://bugs.freedesktop.org/show_bug.cgi?id=73074
rhbz#1063170 at https://bugzilla.redhat.com/show_bug.cgi?id=1063170

A proposal of patch is at http://cgit.freedesktop.org/libreoffice/core/commit/?id=740fe0ce142c521d3a75558dea6535017821e127

Description of problem:
When sending a document as an email, at least evolution will create the email with the url-encoded document title as subject.

How reproducible:
Every time

Steps to Reproduce:
1. Create a document with a space in it's file-name
2. File -> Send -> document as email
3. Note how the email subject has the space exchanged for %20

Reproducible: 

Steps to Reproduce:
Comment 1 Bruno Cornec 2014-03-24 09:17:09 CET
I can confirm that rebuilding mga4 libreoffice with the above mentioned patch indeed fixes the issue. I pushed it for an update.
Comment 2 Bruno Cornec 2014-03-24 09:33:22 CET
Both svn ci and mgarepo submit have been done for branch mga4
Comment 3 Manuel Hiebel 2014-05-11 16:31:30 CEST
Can go to the QA then, no ?

Or a new updates planned thierry ?

CC: (none) => thierry.vignaud

Comment 4 Thierry Vignaud 2014-05-24 16:31:41 CEST
latest 4.1.x branch release is 4.1.6.2 but we might want to just push 4.2.x (see bug #12705)
Comment 5 Thierry Vignaud 2015-02-02 20:54:42 CET
Can you try LO-4.3 from updates_testing?

Keywords: (none) => NEEDINFO

Comment 6 Bruno Cornec 2015-02-21 20:18:51 CET
I'd be happy to test it, especially as I now have another anoying bug (https://bugs.mageia.org/show_bug.cgi?id=15340), but there is no LO-4.3 in update testing as of now.
Comment 7 Thierry Vignaud 2015-02-21 23:37:16 CET
It has been pushed as an update a couple hours ago:
http://advisories.mageia.org/MGAA-2015-0012.html
Comment 8 Thierry Vignaud 2015-02-24 12:57:59 CET
Ping?
Comment 9 Samuel Verschelde 2015-09-21 13:20:53 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 10 Marja Van Waes 2015-10-27 06:58:03 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD