This is a bug report based on a comment in bug 60769 (https://bugs.freedesktop.org/show_bug.cgi?id=60769#c25)
How to reproduce:
* download https://www.dropbox.com/s/v4zf2g4aexp1oc9/CanNotWriteBugOSX_LO18.104.22.168.odt
* Open it using LibreOffice
* Just edit the document so you can save it again (I add 1 space somewhere in the text)
* Save it
Result: Error "Could not save document, error in writing sub document context.xml"
Here your bug report about the bug you're dealing with.
1) can you reduce the file size with an older version of LibreOffice which you can't reproduce this behavior with?
2) if you can't reduce the size of it, can I have your permissions to upload to our ownCloud service? http://owncloud.documentfoundation.org/
Because, if you delete that file from dropbox now, we can't access it anymore.
PS: I mark this as new because I can reproduce this behavior, tested using Mac OSX 10.9 with LibreOffice 22.214.171.124.
Hi Joren, I found the bug. I reduced the ODT to the page where the bug is.
You can download the file from my dropbox and but it on your cloud.
Steps to reproduce the bug.
1. Open it.
2. Add a dot.
3. Save it. > Error
Steps to fix it:
1. Open it.
2. Delete the last and the second last image.
3. Save it. Success
So it's corrupt image that is still correctly displayed.
This related to another old problem of LO and OO with images where LO and OO loose the image data.
By the way I have lost images problem very often in Impress too. Specially with
Thanks for you help.
(In reply to comment #2)
> Hi Joren, I found the bug. I reduced the ODT to the page where the bug is.
> You can download the file from my dropbox and but it on your cloud.
> Steps to reproduce the bug.
> 1. Open it.
> 2. Add a dot.
> 3. Save it. > Error
> Steps to fix it:
> 1. Open it.
> 2. Delete the last and the second last image.
> 3. Save it. Success
Well, I fail to reproduce a success by deleting the second last and last images. I did delete a couple of pages, that succeeded too. But no consistent behavior. I did delete all text/images before page 80 -> succeed to save. So then "should" be the problem in this first 80 pages... but when I delete all pages after page 80, and save, it succeeds too.
So there is something really strange going on with this document. Looks like more then 1 single error (just a paragraph, image, ...) it is an error related to the whole document.
@QA members/developers: you can find this document too in OwnCloud (https://owncloud.documentfoundation.org/index.php/apps/files?dir=/Shared/Common/QA/Bugzilla/Bugs/72129) (ps: account required)
Joren : I have encountered similar file corruption on a simple, 10 page ODT file (just text, no images or anything fancy other than a page footer with inserted page number field) that I was translating for work - however, I do not get the subdocument error message, just a general IO error message, and the resulting file can not be subsequently opened in any version of OOo/LO/NeoOffice, or even on other OSes (tried with Linux). The file is also unreadable by unzip.
As my symptoms are not exactly the same as the ones described here, I will open a separate bug report.
(In reply to comment #4)
> As my symptoms are not exactly the same as the ones described here, I will
> open a separate bug report.
Also note that in my case, I was writing to an external USB connected FAT drive
(In reply to comment #4)
> just a general IO error message
Right. Tested using Linux Mint 17 x64 with LibreOffice Version: 126.96.36.199.alpha0+
Build ID: 5bd241b99b76ae7f4b3c1d4f2bcbaf7c487bb339 I also only get a message when opening the file:
Error reading file.
So that "could not save document" error is probably Mac OSX only.
> the resulting file can not be subsequently opened in any version of
> OOo/LO/NeoOffice, or even on other OSes (tried with Linux). The file is also
> unreadable by unzip.
That is strange, because Archivemanager (default unzip program of Linux Mint) can unpack it without a problem.
Created attachment 111145 [details]
File for test
I started to get this bug since the LibO4.4.0 beta version. I waited for the RC1 version to see if the bug is off. Unfortunately, it's still there.
Neverthelesss, I can save to a "doc" format with some data loss.
To my point of view, it's quite annoying to have this message. Having numereous documents, when edited with this version to make some modifications, I can no more save to my HD.
Save can de done with the LibO4.3.5 version.
I included one of my files to enable you to have a test on it.
Hope that this will help. Feel free to ask for more details.
I ommited to indicate that I'm under UBUNTU 14.10 X64 - LibO4.4.0 RC1
Maybe these details can help.
attachment from comment #7 was fixed by commit 97952280f0adbe195e6a2e0bab8a21a7e352a721
*** This bug has been marked as a duplicate of bug 86963 ***
eeh... wait a second... this was reported 2013-11-28?
then it can't be a duplicate of 86963 because the textbox-shape code didn't exist back then?
... oh it looks like email@example.com has hijacked the bug ...
let's undo that...
how do i get the bugdoc that is actually relevant here? the URL from description and comment #2 is 404.... how
Comment on attachment 111145 [details]
File for test
irrelevant to this bug
cloph told me the goodies are at a different URL:
tried various different versions incl. 188.8.131.52 on Linux x86_64,
cannot reproduce the problem...
there's a lot of images, maybe needs too much RAM on 32bit?
hmm.... can see 4.1 soffice.bin with ~2G RES... that could be an issue...
bug 73300 comes to mind, which was fixed in 4.1.6
does this problem still occur with current 4.2.8 / 4.3 versions?
Thanks Michael for checking. I also can't reproduce it anymore using LibreOffice Version: 184.108.40.206
Build ID: a3603970151a6ae2596acd62b70112f4d376b990
-> RESOLVED WFM
Just happened for me with LibreOffice 220.127.116.11 on MS Windows. I was editing DOC file (no, I cannot send it unfortunately), saving it as DOC. When trying to save as ODT (so that images stay where I put them), I got this error.
LibreOffice doesn't crash, and I still can save it as DOC.
Fail to reproduce; so lets mark this bug as resolved worksforme.
Tested using Windows 7 x64 Enterprise
Build ID: 50336412f775af154509d67b1ebbdb4b5feb147b
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2016-03-10_08:03:20
Locale: nl-BE (nl_BE)