Bug 408774 - Okular refuses to save document when original file has been (re)moved or changed
Summary: Okular refuses to save document when original file has been (re)moved or changed
Status: RESOLVED DUPLICATE of bug 402017
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 1.7.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-16 11:22 UTC by grmat
Modified: 2019-06-16 22:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description grmat 2019-06-16 11:22:02 UTC
SUMMARY

An opened file can't be saved to a new location once the original file has been (re)moved or changed.

This often happens for "temporary" files directly opened from a web browser or mail client.



STEPS TO REPRODUCE
1. Browse the web, open a PDF file in Okular directly from the browser (which usually results in the file stored into /tmp)
2. Fill a form or annotate the file
2. Close the browser (which results in deletion of the file*)
4. try to save the annotated file to a new location (save-as)

*as opposed to overwriting the original file, this doesn't even trigger a warning inside Okular



OBSERVED RESULT
Okular shows a pop-up:

The file 'test.pdf' has been modified by another program, which means it can no longer be saved.

and refuses to save the file. The work is lost, even though it's still there, right in front of the user's eyes.



EXPECTED RESULT
The modified file can still be saved to a new location


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.16.0-1
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2019-06-16 22:29:23 UTC

*** This bug has been marked as a duplicate of bug 402017 ***