I’m currently quite frequently, if docs are getting bigger, but not reproducible, getting “read errors” for embedded pictures in frames, after opening an odt writer file.
At first, instead of the original picture an empty frame is shown, with the text “read error” and some sort of “broken” symbol aside to text. Clicking on the frame let it disappear, no further message.
*** UGLY *** about this bug is, that it can happen during a writer session, or after opening. And if it happens, the file on disk is already (!!) damaged - no chance to exit without saving !!!
As I’m the “paranoid” guy using all on SSDs and that’s why performing daily incremental backups, I haven’t had that much data loss. But it’s still painful and not really reliable.
Any ideas/hints how to narrow down this bug?
BTW where are LO bugs tracked?