Created attachment 144749 [details] I open the file on the left of Okular. Okular opens a .png image I have on my desktop. SUMMARY *** I have two PDF files with invoices. Both start with the character # (example: #FA2185.pdf) Okular does not display the content of the document. Instead, it opens an image I have on my desktop. When I remove the # character from the file name (#FA2185.pdf to FA2185.pdf) Okular opens the document correctly. *** STEPS TO REPRODUCE 1. Rename the PDF file by inserting the # character at the beginning of the name. 2. Open the file with Okular. 3. Unexpected result, the real content of the PDF-file does not appear. OBSERVED RESULT The visible result does not match the document. Okular obtains the visualization of a compatible file that is located in the same path (folder) where the PDF document we want to visualize is located (in my case, it is the desktop). EXPECTED RESULT Display of the actual PDF content. SOFTWARE/OS VERSIONS Windows: 10 21H2 Compilation 19044.1415 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Okular Versión 22.03.70 S.O. Language: Spanish
I think this is related to specifying the page after a # sign, like 'some_document.pdf#15'. That feature is available for all platforms, but I can not reproduce this issue with KDE Neon user edition. I do not have Windows. Two questions which might help others to reproduce this: The properties dialog seems to show that Okular actually managed to “open” the desktop, and got this 0 byte image then. Can you describe this image a bit more? Is it some special kind of file? How did you launch Okular? Double-click the desktop icon of the document you want to open?
(In reply to David Hurka from comment #1) > I think this is related to specifying the page after a # sign, like > 'some_document.pdf#15'. > > That feature is available for all platforms, but I can not reproduce this > issue with KDE Neon user edition. I do not have Windows. > > Two questions which might help others to reproduce this: > > The properties dialog seems to show that Okular actually managed to “open” > the desktop, and got this 0 byte image then. Can you describe this image a > bit more? Is it some special kind of file? > About the image file: It was the only file other than desktop shortcuts. In another test, in a different folder, Okular showed each of the images from the folder where the pdf file was and also from the folders nested below. The image file is a PNG file with 500 x 500 px transparency. > How did you launch Okular? Double-click the desktop icon of the document you > want to open? Exactly so I did. Double click on the .pdf file to view it with Okular
I did the same check (same PDF files) on Linux Ubuntu Studio 21.10 and Okular 21.08.1. It worked correctly, so maybe that problem only occurs on Windows.
> In another test, in a different folder, Okular showed each of the images from the folder where the pdf file was and also from the folders nested below. Ah, I think this is the CHM / Comic Book / Fiction Book / whatever backend. One of these “opens” a directory and displays all the images in it. It is intended for books where each page is an image file in a common directory. Can you confirm this by reproducing the issue and going to Help -> About Backend?
Created attachment 144852 [details] "ComicBook Engine version 0.4". Indeed, the backend informs about the "ComicBook Engine version 0.4".
Have you tried with a newer Okular version? At least this works fine for me on Windows11 https://imgur.com/a/Q9WjB8i (sorry for the potato quality video)
(In reply to Albert Astals Cid from comment #6) > Have you tried with a newer Okular version? > > At least this works fine for me on Windows11 https://imgur.com/a/Q9WjB8i > (sorry for the potato quality video) I haven't used W10 for documents lately, so I didn't test the new version. My PC cannot be upgraded to W11.
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!