When LO is started after a crash, it offers to restore/recover files from before the crash.
In some cases (or maybe always?), when a file intended for recovery is not found, LO opens multiple dialogs saying as much.
At the very least, LO should keep it to a single notice of failure per file.
Also, one could argue that no extra dialog should be open other than the recovery dialog, where the failed recovery item gets an 'X', and some extra UI (e.g. hover-based comment, expandable widget with a label) could tell the user what the failure was.
*** This bug has been marked as a duplicate of bug 114508 ***
This is a different issue than 114508; it doesn't involve the user choosing to discard.
Any way to reproduce they described case and or some context when this happens
Reproduction instructions which may or may not work for you...
1. Open LO writer.
2. Type in some text.
3. Save the file as test-01.odt
4. Save the same file as test-02.odt
5. Use kill -KILL to kill the LO processes (don't exit normally)
6. Delete the two files you saved.
7. Start LO, wait for the recovery dialog to come up.
8. Wait 3 seconds
9. Press Start
10. A first message box appears, about the first file; wait 3 seconds
11. Switch back and forth between the recovery dialog and the message box
12. Dismiss the first message box
13. A second message box appears, about the second file; wait 3 seconds
14. Switch back and forth between the recovery dialog and the message box
15. Dismiss the second message box
16. A third message box appears. It says: "Object not accessible. The object cannot be accessed due to insufficient user rights".
17. The Start button on the recovery dialog changes to Finish and becomes active.
18. Click Finish.
19. LO comes up.
Un-closing and renaming to clarify this is not about what happens when you discard, but rather when you try to recover.