https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #41 from David Hurka <david.hu...@mailbox.org> --- > I mean think of this message you would have to show the user "Sorry, we > can't open your file because you don't have enough space on disk". If there is not enough space to create a temporary copy, how should the file be saved after editing? If the file was streamed-from-disk in that case, it would have to be deleted in order to save the edited version. But then, nothing can be saved anymore, so I don’t see the point to not create temporary copies. So I make another suggestion: C) Create temporary copies of any file. But if there is not enough space to make a temporary copy, consider the original file to be the temporary copy (but remember to not delete it). D) Like C, but also remove swapBackingFile. I think full reload instead of swapBackingFile is acceptable in this corner case. (If that would lose e. g. annotations, the user could still save to .okular first.) ... Hmm, okay, the user could still save to a remote location. -- You are receiving this mail because: You are the assignee for the bug.