Description: In the attached RTF file, the first image isn't rendered correctly. And when saving it to an external file, only a small part of the actual image is used. The correct image can be seen by loading the second attached file, which is a .docx version of the first one, saved using MS Word. Steps to Reproduce: Load attached .rtf file. Actual Results: Image is corrupt. Expected Results: Image should look like in the .docx file. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Created attachment 142122 [details] RTF file to reproduce the problem
Created attachment 142123 [details] DOCX file which is loaded correctly
I should have noted that the problem is still in present in LO 6.0.3.2.
Confirmed on LO 6.0.4.2 (64 bit) on Xubuntu 17.10 (64-bit) Milan, please add info from dialogue Help > About
Created attachment 142412 [details] how it looks in MS2010
I can reproduce it back to Version: 5.0.0.0.alpha1+ Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 Locale: ca-ES (ca_ES.UTF-8) but not in Version: 4.5.0.0.alpha0+ Build ID: 2c5ce8ea8eb98f2d82986448af448d11b60a3ea1 Locale: ca_ES it needs to be bisected with bibisect-50max
I declare this notBibisectable after about 2 hours of trying, having to mostly git bisect skip due to General error in opening. I got as far as "756 revisions left to test after this" (Win 5.0 repo)
A note here, this bug started in two steps, because even before the change in 5.0, the order of images is reversed. In 3.3.0 the order is correct, in 3.5.0.3 the images aren't imported, and in 4.2.0.4 they appear, but the legend is above the chart, while it should be below.
Dear Milan Bouchet-Valat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still repro in Version: 6.5.0.0.alpha0+ (x64) Build ID: 42a1a1c6b91907f81e15066ffab219411f18c4db CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear Milan Bouchet-Valat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in 7.2.4.1.
Created attachment 182166 [details] The example RTF and the DOCX version in current master This seems to have gotten better in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: cba119c2a44bcef4684073412798aec193fbd1b5 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded Previously the blue-orange columns legend image was badly distorted. This got better after: https://git.libreoffice.org/core/commit/57d9cc81b058757421cd082e5dbe32a919716807 tdf#127806: RTF import: use shape dimensions for pib picture But: this is a grouped shape originally, and now there are two instances of the blue-orange chart and its legend image. One set at the top of the first page as grouped shape: - This is anchored incorrectly to the first empty paragraph of the document below the TextFrame with the title. - There is an extra empty rectangle image below it, similar in size as the shape containing the blue-orange legend. And another set as two individual, overlapping images at the top of the second page, these seem to be anchored to the second-to-bottom paragraph, before the page break. This is a correct anchoring, for the wrong objects. Let's refocus this bugreport to the correct import of grouped shapes from RTF.