Created attachment 143276 [details] okular error Running okular-21.08.2-817-windows-msvc2019_64-cl.exe When I open some documents with private information, I get this error: Some errors were found in the document, Okular might not be able to show the content correctly. Any way to debug it without having to share the pdf with private information?
@David Hurka this is different from 444297, that one is about not being able to open the document, this one is just poppler saying "your document is broken, we did the best we could to show it". @Teddy, the only way to debug it without you sharing the PDF is you doing the debugging. Or you can share the PDF with us. I'm going to mark this bug as NEEDSINFO because there is no other way to proceed unless we have the PDF file, and even if we have, the answer you're most probably going to get is what already said "the document is malformed and we're doing the best we can to show it"
How to I debug? I open with "okular file.pdf" but no log to terminal.
To debug this you probably need to compile poppler [ https://poppler.freedesktop.org/ ] and debug it with gdb to figure out what is causing this, unless you're a C++ developer this is mostly outside things you can actually do.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
The PDF file was created with a non-official application. This is the metadata: <?xpacket begin="" id="(removed)"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 7.0-c000 79.1357c9e, 2021/07/14-00:39:56 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:xmp="http://ns.adobe.com/xap/1.0/" xmlns:pdf="http://ns.adobe.com/pdf/1.3/"> <xmp:CreatorTool>PDFsharp 1.50.5147 (www.pdfsharp.com)</xmp:CreatorTool> <xmp:ModifyDate>(removed)</xmp:ModifyDate> <pdf:Producer>PDFsharp 1.50.5147 (www.pdfsharp.com)</pdf:Producer> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end="w"?> Will contact the app developer and see if there's any bug with the program.
issue has been files to proprietary software developer: https://forum.pdfsharp.net/viewtopic.php?f=3&t=4307
Created attachment 144428 [details] metadata properties
okular could provide more useful debug information.
Better debugging capabilities are required.
Created attachment 153267 [details] This files produces the error message in Okular 21.12.3 in Linux Mint You've been asking for sample documents for quite a while, so here's one. I'm able to consistently create documents that make Okular show this error message using Google Drawings. I am using Okular 21.12.3 in Linux Mint. Hopefully this document will help figure out what the problem is and, even more hopefully, the change will make it to the Linux version.
(In reply to alexwi from comment #11) > Created attachment 153267 [details] > This files produces the error message in Okular 21.12.3 in Linux Mint > > You've been asking for sample documents for quite a while, so here's one. > > I'm able to consistently create documents that make Okular show this error > message using Google Drawings. > > I am using Okular 21.12.3 in Linux Mint. Hopefully this document will help > figure out what the problem is and, even more hopefully, the change will > make it to the Linux version. As mentioned in https://bugs.kde.org/show_bug.cgi?id=461129 that document is malformed, so yes, we show a warning about it.