https://bugs.documentfoundation.org/show_bug.cgi?id=164332
--- Comment #5 from achim <[email protected]> --- Hmm, the reported problem *does not* "breaking the working of the software". The "rm" in my example was used to provide a very simple example to reproduce the situation. The mentioned file may disappear for various reasons. Such a situation is not handled by LO appropriate, but bothers the user with wrong and not really understandable error messages beside loosing data. Please see my "Expected Results". IMHO it's a bad habit to blame the user for trapping into software bugs, just because something happend the programmer didn't expect :-( Other suggestion, if you won't fix the bug: Please write a detailled description what these messages mean, how to prevent them and how to solve the problem, probably in the LIMITATIONS|KNOWN ERRORS section. Feel free to decide what's the better approach: documentation or fixing the bug. Please reopen the bug. Please don't get me wrong: it's not about blaming the programmers for not expecting "something". But now there is an example what should be expected. Hope this helps. -- You are receiving this mail because: You are the assignee for the bug.
