Created attachment 170904 [details] Upper images: Orignal cropped Bottom images: Original cropped after compression 1 - Create a document and insert a JPG or PNG image with a dpi > 75dpi (more higher, more visible is the issue) 2 - Crop image only vertically or horizontally at half size 3 - Compress image Result: Image is compressed but it lost aspect ratio. I think is a calculation error inside compress process
I can't confirm it with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 15a9bee9ef26ce13ed1e26319306a88b6d886158 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL and also not with Version: 7.1.3.1 (x64) / LibreOffice Community Build ID: fa76d07d7006a0e2866c3247cef2d5eb55ae8369 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded I openeed attached document but for every image aspect ratio looks O. K.
You must compress the original (upper row) tiger photo to see the issue. Just when you do it, image will appear narrowed horizontally.
Created attachment 171464 [details] Screenshot after compress bottom row images
There might be a similar bug in meta bug 116082 (it also depends on screen resolution. Which screen used to create & which screen used to compress)..
(In reply to rafael.linux.user from comment #2) > You must compress the original (upper row) tiger photo to see the issue. > Just when you do it, image will appear narrowed horizontally. O. K. Now I could see it (it wasn't as a much as I expected). I changed DPI from 300 to 150 Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 15a9bee9ef26ce13ed1e26319306a88b6d886158 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
*** Bug 143151 has been marked as a duplicate of this bug. ***
Checked with bibisect repos and this is there since 4.1, so same as bug 83734. I understand that Mike didn't close as duplicate because there is some difference in the bug descriptions.
I think we can confidently close as a dupe of bug 83734. *** This bug has been marked as a duplicate of bug 83734 ***