Suppose that you have a jpg image in a presentation slide in impress and that you want to recompress it because your presentation file is too large.
You can achieve this result with the 'compress' function in the context menu for the image. Unfortunately, if the image is cropped, compress often breaks the cropping, resulting in distorted images.
Steps to Reproduce:
User Profile Reset: No
[Information automatically included from LibreOffice]
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
The same problem was reported in bug 99265. That was resolved duplicate to bug 99286, which is fixed now. But the problem described here still exists. I see it in Version: 22.214.171.124.alpha0+ (x64)
Build ID: 55b9706bea5aa9b654ab39bc7d56339422e17087
CPU threads: 8; OS: Windows 10.0; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-04-18_06:02:46
Locale: de-DE (de_DE); Calc: CL
Problem: The original image is reduced in quality and DPI as chosen in the dialog. But the crop values are totally wrong, which results in a distorted image.
Created attachment 141521 [details]
No repro with
Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737
CPU Threads: 4; OS Version: Windows 6.2; UI Render: default;
Locale: en-US (nl_NL)
This looks like bug 83734 except bug 83734 comment 17 insists on a separate report
Repo in 6.1 master and Version: 126.96.36.199
Removed the "regression" keyword. Also, I fail to see how this is not a dupe of bug 83734. Steps to reproduce are identical, just different components.
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!
The bug is still present as of LibO 188.8.131.52
I agree with Telesto. This is a dupe of bug 83734. It's a graphics stack issue not impress specific.
*** This bug has been marked as a duplicate of bug 83734 ***