Summary: | Files lost after being told they cannot be saved | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | bark mallard <markjballard> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | yurchor |
Priority: | NOR | ||
Version: | 1.3.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | attachment-461-0.html |
Description
bark mallard
2020-05-11 15:43:35 UTC
I guess this bug report also can be named "Firefox deletes temporary files when it wants to do so". It is unsafe to use Okular for editing or viewing such files without immediately saving them outside the temporary folder. Am I right? Created attachment 128365 [details] attachment-461-0.html > --- Comment #1 from Yuri Chornoivan <yurchor@ukr.net> --- > I guess this bug report also can be named "Firefox deletes temporary files > when > it wants to do so". It is unsafe to use Okular for editing or viewing such > files without immediately saving them outside the temporary folder. > > Am I right? > > Of course not! You are passing the buck! When Okular takes the file from Firefox, it assumes responsibility for the care of that file. If I, as a user, find that Okular prevents the file being saved, then Okular has failed me. And as a user with some experience, I can say this error seems unique in all that experience, and it seems logical to expect that as file that is open is a file that can be saved, regardless of what happens to the underlying file, just as with any text editor. We don’t need to evaluate how Okular should behave when files are deleted, we already did that in the other bug. I don’t know how to fix this; the fix is already in production code, but I don’t know why it doesn’t work. Maybe it is just that people compile Okular without OKULAR_KEEP_FILE_OPEN? *** This bug has been marked as a duplicate of bug 402017 *** |