Created attachment 187323 [details] File before export PDF: After export excel file to pdf with option "Whole Sheet Export" and got empty pages in resulting pdf. Steps to Reproduce: 1. Open Calc 2. Select menu File->Export to PDF 3. Select Whole Sheet Export 4. Open resulting pdf and there will be empty pages Actual Results: Not correct result of exporting file to pdf with option "Whole Sheet Export". Expected Results: Correct exporting file to pdf with option "Whole Sheet Export" where each sheet will be on exactly one page.
Repro using Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded The PDF pages contain a *part* of the data, located at the bottom right corner of mainly empty pages. Looks as if the page size was detected correctly, but then the data was put with a huge offset both down, and to the right.
There is no offset, just *part* of the data not displayed, but page size was detected correctly.
Problems with the example file also occur with Print preview (Ctrl+Shift+O). Scale set too small for printing.
Still reproducable in LO 24.2.0.0 alpha release under Windows 10(x64). Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 695ae365dcab7c7dd59b39411299c5c200081885 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded
Still the case in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9574a62add8e4901405e12117e75c86c2d2c2f21 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Already the case in: Version: 6.4.0.3 Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded so marking as "implementation error".
Dear phoekoby, 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
*** This bug has been marked as a duplicate of bug 134229 ***