SUMMARY I open a PDF (v1.6), highlight a word, save using CTRL+S (same using File -> Save): Okular crashes. STEPS TO REPRODUCE 1. Open a PDF (v1.6) 2. Highlight a word 3. Save document with CTRL+S OBSERVED RESULT Okular crash without saving the modified PDF file. EXPECTED RESULT Okular save the PDF file and not crash. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro (version: 20H2)(Build: 19042.746) ADDITIONAL INFORMATION Okular installed via scoop.sh (scoop install --arch 64bit okular)
I can’t say anything about windows stuff. But interesting questions may be: 1. Does it crash when you don’t modify the PDF file, and save with “Save as...”? 2. Do you get console output when you start Okular from a command line? 3. > Summary: Win10Pro 64bit: Okular crash without saving the modified PDF file. Does it work fine on other windows versions? Otherwise, the version is not necessary in the summary. 4. > Component: PDF backend Does that mean it works fine with other document types? You can try to open an arbitrary .txt file, save it as .okular archive, and then repeat steps 2 and 3 there. 5. > ADDITIONAL INFORMATION > Okular installed via scoop.sh (scoop install --arch 64bit okular) That probably means: > "64bit": { > "url": "https://binary-factory.kde.org/view/Windows%2064-bit/job/Okular_Release_win64/529/artifact/okular-20.12.1-529-windows-msvc2019_64-cl.7z", > "hash": "9614cb2785d43bd5dc240a30c79d581d4ecb3f3e75fa5bb06fbb57ac32407870" > } https://github.com/lukesampson/scoop-extras/blob/master/bucket/okular.json I. e. it just installs a precompiled version, which is probably fine. This script seems to be updated daily. Possible that only the version from yesterday was affected.
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!
After the 20.12.2 update the bug was solved.