Created attachment 44789 [details] File where images get read error. This is, or is related to BUG 33051 but is fully repeatable for me on 2 machines and LO 3.3.0 - 3.3.2. https://bugs.freedesktop.org/show_bug.cgi?id=33051 I had this bug in OOO when I went from 2.4 to 3.0 so I went back to 2.4. The next release after 3.0 fixed it (in that case). Symtom: When a writer file with images is changed and then auto saves the image shows "Read-Error" and if the file is then Saved the image is lost from the saved file. This is happening on 2 X86-64 machines, Suse 11.0, LO 3.3.0, 3.3.1, 3.3.2., OOO 3.2.1 It is not happening on my Mac. Case:1 If the file is opened and changed and left to autosave 2 images show "Read-Error" and if the file is then Saved the image is lost from the saved file. 1 image is a JPEG, one a PNG. Case:2 If the file is opened and saved immediately and then changed and left to autosave, the images do not get "read-error" (so far). This was first noticed happening (I am fairly sure) on a file last edited in LO 3.3.1 on a Mac, it is also happening on other files edited in linux which prior to my moving to LO seemed fine in OOO. Are there any shared libraries that could have been updated by LO?. To reproduce, go to the page numbered 14 in the attached manual. Change some text and wait for an autosave. The DB9 connection diagram on the right gets a read error every time for me. As an asside, the table to the left of the diagram has 3 digits in the left column that don't transfer with the file from my mac (little squares)- investigating but interested to have it confirmed.
If I "save As" a new file name from the mac, this problem still occurs in linux with the new file. If I "save As" the mac file with a new file name from linux this problem does not seem to happen in linux.
This one might be a DUP of "Bug 33393 - After autosave image shows read-error and will be lost on save". It seems that I can reproduce the bug. @Steve Edmonds: what do you think?
I think it is a duplicate, I even commented in the other bug. Don't know why I didn't link the 2. *** This bug has been marked as a duplicate of bug 33393 ***