Description: DOC: Image dimensions wrong form image with border Steps to Reproduce: 1. Open the attached file 2. Notice squeezed images (opens fine in MSO) Actual Results: Squeezed Expected Results: Proper Reproducible: Always User Profile Reset: No Additional Info: Found in 7.2 and in 4.4.7.2 and in Version: 4.3.7.2 Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba but not in 4.2
Created attachment 169270 [details] Example file
Created attachment 169271 [details] Source ODT
Confirm this Tested with Version: 5.4.7.2 -> not working Build ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk2; Locale: ro-RO (ro_RO.UTF-8); Calc: group Working in Version 3.6.7.2 (Build ID: e183d5b)
This regressed in two steps. First the image wasn't shown at all after the following commit in 4.2 (commit ported from AOO): https://cgit.freedesktop.org/libreoffice/core/commit/?id=2e5167528f7566dd9b000e50fc1610b7bf99132a author Armin Le Grand <alg@apache.org> 2013-10-31 14:43:21 +0000 committer Caolán McNamara <caolanm@redhat.com> 2013-11-05 15:24:18 +0000 "Resolves: #i123500# unified Graphic processing to use GraphicPrimitive2D" Then that got fixed with this commit in 4.4, but the image was now imported squashed: https://cgit.freedesktop.org/libreoffice/core/commit/?id=6d431ffb682d0e64b75b6267f369822ff0b0617e author Michael Stahl <mstahl@redhat.com> 2014-05-24 18:02:31 +0200 committer Michael Stahl <mstahl@redhat.com> 2014-05-24 18:34:06 +0200 "fdo#77454: fix WW8 import/export of negative image crop The negative crop values were imported as large positive values, which caused the image to be rendered with 1 pixel width after commit 2e5167528f7566dd9b000e50fc1610b7bf99132a."
repro 7.6+
Dear Telesto, 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
Repro Version: 25.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c854f5aaae575a0570f79a225b80b53ed420578c CPU threads: 8; OS: macOS 14.7.4; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded