SUMMARY STEPS TO REPRODUCE 1. Open PDF file in Okular 2. Select "Print Preview" command (ie under under "File" menu) OBSERVED RESULT Window will become unresponsive and shortly crash EXPECTED RESULT Trigger window to preview the expected print. If this requires additional setup first (ie an addon, backend, or additional program be installed), present a warning to the user and stop execution. SOFTWARE/OS VERSIONS Windows: Windows 7 (Version 6.1.7601 Service Pack 1 Build 7601) KDE Plasma Version: N/A (Windows windowing system(?)) KDE Frameworks Version: KDE Frameworks 5.63.0 Qt Version: Qt 5.13.1 (built against 5.13.1) ADDITIONAL INFORMATION Okular was installed from the latest release executable before reporting; thus far reproducible across multiple pdfs of varying size.
I will unfortunately be unable to reproduce from here on; my work is upgrading all of us to Windows 10 now, so I will no longer be on Windows 7 from here on.
Please someone reopen if you have the same problem.
After upgrading to Windows 10, and installing the release available in the Windows Store, I am actually still encountering this issue.
*** Bug 414937 has been marked as a duplicate of this bug. ***
Yes, this still happens. I uploaded today the 19.12.2 version to the store, but this will not fix this issue. It either hangs infinite or crashes, will need to investigate. e.g. Kate that uses the same Qt version doesn't hang on that action, should be no issue in Qt itself.
Actually printing (at least to my only available "one note" printer) hangs, too.
Ok, I must re-consider: actually printing (to one note) does just take "long" here, aka one minute for my test document that has ~200 pages. But Okular recovers after that time and stays usable afterwards. Not sure if the preview dialog does that same, will let it run a bit longer ;=)
Ok, print preview doesn't really hang infinite either, after 2-3 minutes for my large document I get a dialog with "Could not load print preview part". After closing that, Okular is usable again. Not that this is the perfect workflow one would expect, but perhaps this helps a bit to trace back the issue.