1. Open a PDF file 2. make some annotation 3. save as... to create a new PDF containing the annotations 4. close & reopen okular 5. open the new PDF file 6. make some annotation 7.1. close okular: it asks to save or discard the new annotation (after <https://bugs.kde.org/show_bug.cgi?id=269819>) 7.2. crash okular (a bug, or simulate with SIGKILL/kill -9): the new annotation is lost
Sorry, but I don't get it. I am supposed to crash okular while the "save or discard annotation" window is open? That is before the annotation is saved, so of course it is lost. What am I missing?
@Oliver: sorry for the confusion. 7.1 and 7.2 are alternatives: 7.1 means when you close okular normally, it asks for saving. If you don't close okular, but crash it, the annotation is lost
But isn't that what other programs do as well? If you crash a program before having saved your modifications, then those modifications will be lost.
Of course, but still we could do better :) Especially since annotations are only lost on crash if the file already contains some previous annotations: If it doesn't, okular instantly saves new annots in docdata/ which preserves them even in case of a later crash.
Doesn't really convince me. Feel free to post patches, but I tend to consider this not a bug.
Yeah, the bug here is that Okular crashed, not that the annotations didn't get saved before you could complete the Save function. Okular shouldn't have crashed! :)