Created attachment 106084 [details] Sample document with a cropped image How to reproduce: 1 Load the sample document with the cropped image (only green half visible) 2 Right-Click the image, choose Compress Graphic... 3 Choose OK (default settings will do) Expected result: Cropped part (red) still invisible Actual result: Part of the cropped right half (red) of the image becomes visible Bug observed in: LibreOffice 4.1.6.2 on openSuSE 12.3 (64-bit) LibreOffice 4.3.0.4 on openSuSE factory (32-bit) LibreOfficeDev 4.4.0.0.alpha0+ on openSuSE 12.3 (64-bit) Build ID: 53425404ae70bf365073cce2f5d576b769446c97
Thank you for this bug report. Reproducible for me with version 4.3.3.0.0+ built at home under Ubuntu 14.04 x86-64. Best regards. JBF
Here, too. Version 4.4.2.2 on Ubuntu 15.04. (Actually have seen on any version of Ubuntu + any version of LO that I have used for the last 3 years.) I found that when multiple images are inserted in writer/impress, it becomes quite slow. I would say it is slower than what I would expect from MS office, or Mac applications with similar systems. I guess Libreoffce tries to give more control to users not just performing arbitrary compression. That I like, but I think that approach is not complete until all image information are safely kept over this and that modifications to images. I always appreciate your work, LO team. Cheers, Hoseung
Reproduced in Lodev: Version: 5.1.0.0.alpha1+ Build ID: c8ee3be0e08c435b106f0ac4b76618b33333b040 Locale: en-GB (en_GB.UTF-8) on openSuSE 13.1 (64-bit)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Reproduced in LOdev: Version: 5.3.0.0.alpha0+ Build ID: 075489b4b810692edc2ba9910eb3ca659a2b6745 CPU Threads: 4; OS Version: Linux 3.12; UI Render: default; Locale: en-GB (en_GB.UTF-8); Calc: group Actual result is worse than reported before: Severely distorted picture only becomes visible after undoing the cropping on the left hand side.
I conform the problem with compressed JPEG pictures in 2 variations: * The compressed picture disappears completely. * The compressed picture will be very small but the picture frame remain the same so that the compressed picture has the same height and witdh as before but the most space is white and the original picture is a small picture in the white picture. But not all JPEG pictures are affected. Version: 5.1.4.2 (x64) Build-ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a CPU-Threads: 8; BS-Version: Windows 6.19; UI-Render: Standard; Gebietsschema: de-AT (de_DE)
Created attachment 128090 [details] Distorted compressed image LO 5.1.4.2 (x64)
Isn't such bug a regression that should be fixed in a new version like 5.3? The bug makes a feature available in a right-click menu unusable.
Created attachment 131240 [details] Test file with different images (cropped and not) Tested it with the current version 5.3.0.3 and found out that the bug still exists. I created a test file with 3 different images and all cropped and not cropped. Résumé: Only cropped JPEG photographs that were NOT manipulated with image manipulation programs like GIMP are affected (see page 2, manipulated JPEG images see page 1). Only cropped PNG images that are cropped with "JPEG quality" (and not with "PNG compression") are affected (see page 3). Version: 5.3.0.3 Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; Locale: de-DE (de_DE); Calc: CL
Added keyword possibleRegression because the picture compression feature worked without that problem in former versions but I don't know when it began to do what's described in this bug report.
i confirm the bug on libreoffice 5.3.3.2 under windows 10. If you first make a compression of the image and then crop it there is no problem.
It seems that fixing of Bug 99286 "Cropped image disappear after compress" fixed the main problem of attachment 131240 [details] but that doesn't touch the problem described by the bug opener and shown in attachment 106084 [details]. In attachment 131240 [details] I still also see this problem of "horizontally shrinking" of the cropped image so that former cropped part of the image is seen after compressing it. Version: 5.4.1.2 Build-ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU-Threads: 4; Betriebssystem:Linux 4.10; UI-Render: Standard; VCL: gtk2; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group
*** Bug 96726 has been marked as a duplicate of this bug. ***
*** Bug 113116 has been marked as a duplicate of this bug. ***
The bug 99286 DID NOT solve this bug. See the bug 113116 and the last comments in the discussion of the bug 99286 for test-cases that the bug is still present in 5.4.2.2 and 6.0.0.0.alpha0+. (BTW, the bug 113116 was marked as CONFIRMED before being marked as duplicate; so this one should be CONFIRMED too; although I'm not sure if it was correct to mark as duplicate, because this one is about 4.1.6.2 and that one was said to be a "regression introduced in the 5.0 cycle".)
The same happens on Impress (LO 5.2.7.2) when applying compress after crop; the other way round works ok. Should I open a specific bug for Impress? The two might be related to the same upstream problem
(In reply to aflux from comment #16) > The same happens on Impress (LO 5.2.7.2) when applying compress after crop; > the other way round works ok. > > Should I open a specific bug for Impress? The two might be related to the > same upstream problem Please test with a current 5.4 LibreOffice and create a new bug for Impress if it's also affected. Add this bug to "See also" and please add the same blocking bugs to the new bug. Thanks!
Created attachment 141524 [details] Impress .odp with a cropped image I highly doubt this is a separate bug as the steps to reproduce and the results are identical in Writer and Impress. Still reproducible in Version: 6.1.0.0.alpha0+ (x64) Build ID: d4a01820ae094ef2d4ec2196334120600b1c9621
Dear Stephan van den Akker, 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
Reproduced in: Version: 6.3.3.1 Build ID: 30(Build:1) CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kde5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded
Reproduced in: Version: 6.4.0.0.alpha1+ Build ID: 202a49a5831fbfcf057350ef949c13e75b3b7446 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded
Repro LO 6.5+. I set as Major, due to duplicates and uncertainty. I don't know how Compress could be regression, I think introduced in LO 4.1.
not a regression. The enhancement was added in https://cgit.freedesktop.org/libreoffice/core/commit/?id=44faceac60f9046e4827290a85f790a46ed1e227 @Quikee, I thought you might be interested in this issue...
*** Bug 117126 has been marked as a duplicate of this bug. ***
I am not a graphics guy at all. But I think the problem is that SdrGrafCropItem is in 100mm, which is a fairly useless number unless you know the DPI that it is connected with. And the DPI changes constantly in this example - from the initial image's 300-DPI to the compressed images preferred 72-DPI (despite the variable specifying 300). Ultimately, I suspect the biggest problem is that SetPreferredSize is not done with the compression-DPI. The second problem is that we have no idea of the view-size of the image, only the view-size of the cropped part. And the cropped parameters are also based on some DPI - likely based on the GetPreferredSize scale. Specifically, for attachment 106084 [details] from comment 0: In the initial graphic, it reports an original size of 6.77cm x 3.39cm @ dpi 300, but when compressing (still to DPI 300 - the default), then the image properties report a much larger distance (in mm) at DPI 72. However, the scaling knows nothing about this DPI coordinate change from 300 to 72, and so it scales and crops with distances appropriate for 300DPI instead of 72DPI.
attachment 131240 [details] from comment #9 is a really good testcase - creating some very diverse situations. Picture 1 is a tiny image with a huge DPI (according to the properties) and a huge scale factor. The filesize actually increasess when compressed. Picture 2 is a very large image scaled way down. It is very hard to separate the cropping from the scaling... Pictures 2 and 3 are in MapPixel mode. And additional example of finding a picture in MapUnit::MapInch would be good.
(In reply to Justin L from comment #26) > Picture 2 is a very large image scaled way down. It is very hard to separate > the cropping from the scaling... This is the one that really throws me off. What determines how to treat the crop? The coordinates of the crop don't seem to be related to either the pixelsize, the prefsize, or the viewsize. CompressGraphicsDialog CTOR viewSize[7558x11058] crop[-40233x0@(40233,0)] PrefSize[3120x2340] PizelSize[3120x2340] PPI[(72.0006,72)] PrefMode[MapMode(10,((1/1),(1/1))@(0,0))] I'm done with this nonsense.
*** Bug 131174 has been marked as a duplicate of this bug. ***
The same occurring in v7.0.1.2 (2020-10-05), Win 10 x64. Kind of important bug.
Same problem for me. Version: 7.0.2.2 (x64) Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); Interfaccia utente: it-IT Calc: CL
There is an article is about the compressed graphic is used in the program and the cropped image is distorted. I always follow this coding of the program to understand something in it https://best-essay-writing.services/bid4papers-com-review/ this gives me such an understanding program for us and shares your opinion about it.
*** Bug 146044 has been marked as a duplicate of this bug. ***
*** Bug 152163 has been marked as a duplicate of this bug. ***
Still reproduced with: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d1dd9b9733511ff451e264169537c08fa14c574f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded With attachment 131240 [details], the cropped JPG and PNG pictures on pages 2 and 3 have their scaling modified when compressing with the JPG quality option.
*** Bug 141435 has been marked as a duplicate of this bug. ***
*** Bug 158729 has been marked as a duplicate of this bug. ***
Same problem for me. Very problematic bug! Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 12; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded
repro 25.2+ using attachment 131240 [details] from comment #9