Description: When opening the attached PDF files, some pages are blank even though they show up in other applications. Steps to Reproduce: 1.Open the attached file with LibreOffice Draw 2. 3. Actual Results: Page 2 is blank. Expected Results: There was some content on page 2. It should have been displayed Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info:
Created attachment 143974 [details] The pdf file that caused the bug
confirm in Version: 6.1.0.3 (x64) Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: ru-RU (ru_RU); Calc: CL all PDF shows not correct, include empty second page as was in description
Confirmed on Windows 10 Home 64-bit en-US with Version: 6.2.0.0.alpha0+ (x64) Build ID: 7119184f4b5441600f7b3eae7ec6771c094bbb7f CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-07-23_05:38:07 Locale: en-US (en_US); Calc: CL The insert as image filter handles each page of the PDF with correct rendering to canvas (but provides no page selection yet (bug 114234), so have to split PDF externally, e.g. with PDFtk or similar). Also when split apart the pdfio import to Draw of each individual page renders each page fully, with some layering and font weight issues. So, just the filter import/opening of the full PDF shows issues with 2nd and 3rd page of the PDF.
This is a regression from https://cgit.freedesktop.org/libreoffice/core/commit/?id=10290000117b562e3f179c3d1073774dd54cdfee, when poppler was updated to 0.46, thus, this is a bug in poppler. I will report it to their Bugzilla... Closing as RESOLVED NOTOURBUG
Reported in https://bugs.freedesktop.org/show_bug.cgi?id=107517
No problem rendering the file in Evince 3.18.2 or Okular 1.1.3, putting it back to NEW, it must be a LibreOffice problem...
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=10290000117b562e3f179c3d1073774dd54cdfee author Caolán McNamara <caolanm@redhat.com> 2016-08-12 15:19:57 +0100 committer Caolán McNamara <caolanm@redhat.com> 2016-08-14 15:22:35 +0000 commit 10290000117b562e3f179c3d1073774dd54cdfee (patch) tree 7a744a1d41ca05e37cd3935246b48830e6c72c0d parent 32881f01833dbcefd5600e1135dd8743178bfd96 (diff) Resolves: tdf#101460 use most recent poppler release Bisected with: bibisect-linux-64-5.3 Adding Cc: to Caolán McNamara
@Vort, I thought you could be interested in this issue...
Created attachment 144028 [details] Rebuilt source file
It is not necessary to split this file. qpdf 5.1.0 can fix it with simple command (see attachment): qpdf 1.pdf 2.pdf However, when I updated qpdf to 8.1.0, result was quite different: WARNING: 1.pdf: file is damaged WARNING: 1.pdf (xref table, offset 302259): invalid xref entry (obj=344) WARNING: 1.pdf: Attempting to reconstruct cross-reference table qpdf: operation succeeded with warnings; resulting file may have some problems The final file (2.pdf) was empty (915 bytes instead of 284267 bytes for version 5.1.0) So file looks like damaged in some way. And different viewers/editors reacts differently to this problem.
I do confirm the rebuilt file opens correctly in Version: 6.2.0.0.alpha0+ Build ID: c86a47a9d3debbc7e8ee6247f573e7f98c611f19 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded @Vort, thank you very much! Should be consider this as an issue or should be close it as NOTABUG ?
I have tested original file with poppler pdftocairo 0.45 and 0.47 (strangely, there are no binaries available for 0.46) and results were correct. So I guess, there is a chance that this bug can be fixed from LO side.
(In reply to vvort from comment #10) > WARNING: 1.pdf: file is damaged > WARNING: 1.pdf (xref table, offset 302259): invalid xref entry (obj=344) > WARNING: 1.pdf: Attempting to reconstruct cross-reference table Interestingly object 344 [1] is the "KTU STUDENTS" background text being applied to each page. The "rebuilt" version has deleted the object during repair. And, for what its worth, Word 2016 hacks it up pretty badly also on import. =-ref-= [1] <snip> 344 0 obj <</Length 88 /Matrix [1.0000 0.0000 0.0000 1.0000 0.0000 0.0000] /BBox [25.2000 354.5280 586.8000 437.4720] /PieceInfo 349 0 R /Type /XObject /Resources 341 0 R /Subtype /Form >> stream BT 0 0 0 rg 0 0 0 RG 0 w /GS0 gs /F0 72 Tf 1 0 0 1 25.2 365.832 Tm (KTU STUDENTS)Tj ET endstream endobj </snip>
Dear Kuruvilla Mani, 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
still repro with PDf from attach in Версия: 7.0.0.0.alpha0+ (x64) ID сборки: 41177730421f9be9ad955766a5a19667d8003b11 Потоков ЦП: 4; ОС: Windows 10.0 Build 18362; Отрисовка ИП: по умолчанию; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: threaded
Dear Kuruvilla Mani, 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
Still reproducible in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3551d18404cb19cdaa8edb170a549f5c5405d0cb CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded