SUMMARY Okular fails opening PDF supplied by my insurer - Opening in Okular from File menu or run from tty with filename as arg produces an error. File opens OK in Adobe Acrobat in Windoze 10 STEPS TO REPRODUCE 1. Open Okular 2. Open file via File menu 3. Error OBSERVED RESULT Error Could not open file:///home/alan/Downloads/proofofncd.PDF In TTY > okular Downloads/proofofncd.PDF qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1419, resource id: 29360270, major code: 40 (TranslateCoords), minor code: 0 EXPECTED RESULT Should show document SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Leap 15.1 (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION This file shows my name and address so I'm not going to add it as a public attachment. Registered Okular Devs can contact me if required
We can't fix a bug that we can check if it exists. Also opensuse Leap uses a poppler library that is almost 2 years old, the bug may as well not exist anymore
I have produced a readable version so it's not a major problem for me at the moment and, as you say, this bug may have been fixed in later versions of the library. If you are interested in looking into it I can send you (personally) a copy as an email attachment.
Personally not interested, i have lots of things to fix that can be done on public documents.
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!