https://bugs.documentfoundation.org/show_bug.cgi?id=151706
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Justin L <[email protected]> --- (In reply to Dieter from comment #1) > Szenario C: > 7. Remove USB-Stick > 8. Open LO and choose auto-recovery => Doesn't work (expected), but > auto-recovery finished At this point (in Ubuntu/gtk3) with an UNMODIFIED file, I got multiple error notices that the file could not be opened. In the end, the dialog indicated "Recovery Failed" and asked me to press Finish. With a modified file, I see the ODF it created in the backup folder, and recovery successfully retrieved the modified contents (after complaining about not being able to open a lock file). If you would have de-selected that file for recovery, the dialog would have indicated "will be discarded". And that makes sense (comment 2). All non-open documents should not show up on the next RecoveryList, and thus it perhaps should report "Recovery Failed - will be discarded". A windows developer is probably going to need to look into how the RecoveryList is created in this scenario. Does a "task manager kill" trigger a SessionSave in Windows? If this is just a "timed autoRecovery", then one of the steps really needs to be waiting for the creation of the autorecovery file. (If this is not created, then you are just "recovering" from the file saved on the USB - which is no different from an "open". In that case, this is a WONTFIX or WORKSFORME since without a timed recovery file, szenario A and B will no longer request a recovery.) -- You are receiving this mail because: You are the assignee for the bug.
