Create a Draw document. 1. Insert an image there. 2. Right-click it, and select Crop 3. Crop some part from top 4. Select the cropped image, and copy to clipboard. 5. Create a new Draw document, paste there 6. Create a new Impress document, paste there 7. Create a new Writer document, paste there 8. Create a new Calc document, paste there => After steps 5, 6, 7, 8, the pasted image is cropped correctly. === Create an impress document. Repeat steps 1-8. => After steps 5, 6, 7, 8, the pasted image is cropped correctly. === Create a Writer document. Repeat steps 1-8. => After step 7, the pasted image is cropped correctly. => After steps 5, 6, 8, the pasted image is NOT cropped. === Create a Calc document. Repeat steps 1-8. => After step 8, the pasted image is cropped correctly. => After steps 5, 6, 7, the pasted image is NOT cropped. By now, the conclusion is that copying cropped image would always allow to paste cropped image into the same module; when the source is Draw/Impress, it pastes cropped image also into other modules. Now what happens when you copy the *pasted* cropped image (initially originating from Draw/Impress), and try to paste this elsewhere? When such a cropped image, created in Impress, was pasted into Writer, then copied from there, and pasted to other modules, then in all modules, the pasted image is cropped correctly - unlike when the crop was created in Writer! When such a cropped image, created in Impress, was pasted into Calc, then copied from there, and pasted to other modules, then only in Calc, the pasted image is cropped correctly, and all other modules receive uncropped one - just as when the crop was initially created in Calc. The expectation would be that no matter what the source is, and which were the intermediate steps, the cropped image copied into clipboard arrives cropped into any module.
Repro. Already in oldest of linux 43all repo. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 013fbfb592f71c1f0a60b6a7ec08aded375515ac CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 9 March 2023
Dear Mike Kaganski, 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