Created attachment 141169 [details] Source file 1. Open attached ODG 2. Ctrl-A to select all 3. File - Export - Jpeg (tick Selection!!) 4. Default settings, OK The bottom line in the bottom box is cropped away. Not yet seen in 3.6.7. Already in 4.3.0 (tested on Win) Workaround is to export the full page instead of selection in some lossless format like PNG, edit in GIMP to crop how you like and export as JPEG. Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: 6acda2a36c9025e0d3fe94d6ca8788ab60c3203e CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on April 2nd 2018 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
repro 4.1, Linux
Bibisected on Linux with 43all to range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=ae4e4a11d4300f7448cb6bd170fcb034542caddc...4316e643ef345b0f673b4a03a80a4b7cb3185588 It includes the famous mega-commit https://cgit.freedesktop.org/libreoffice/core/commit/?id=44cfc7cb6533d827fd2d6e586d92c61d7d7f7a70 but nothing jumps out at me.
Buovjaga, I tried export only selection from your file into JPG and into PNG in LibreOffice 6.1.0.1 on Windows 10. I got the same result for these both. Bottom line of bottom shape don't crop. There is line. Just border of image very close from this line. Increase scale of image and look at bottom part of image (You can use GIMP). My opinion -> WFM
Created attachment 143549 [details] Screenshot comparing JPEG exports from 3.3.0 vs. 6.2 Maybe it is not cropping, but something changed in the JPEG compression? Earlier the bottom line was clear, but now it looks pale, like only antialiasing. I did take another look at 3.6.7 and it is not full black in it either. 3.3.0 looks sharpest.
Dear Buovjaga, 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
Dear Buovjaga, 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://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
Repro in 7.2.7.2, fixed in 7.3.7.2. Bibisected the fix to Armin's a9f6d98859321e1b9029acc0c6e9347f4c1cf3b7 with linux-64-7.3 repo. Not marking as a duplicate as bug 126319 was a 6.2 regression. Thanks Buovjaga, Armin et al.!