Bug 145281 - [COLLABORA ONLINE] Error in writing sub-document content.xml
Summary: [COLLABORA ONLINE] Error in writing sub-document content.xml
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4 all versions
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-23 12:25 UTC by Jan Bebendorf
Modified: 2022-05-03 11:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Bebendorf 2021-10-23 12:25:14 UTC
We are using Collabora Online and we ran into the "Error in writing sub-document content.xml" error quite often when trying to save an odt document. We've already filed an issue with them and they confirmed that this error is produced by the LibreOffice core (see https://github.com/CollaboraOnline/online/issues/3457).

We are running the collabora/code:6.4.13.3 docker image which ships with LibreOffice core commit 70f6522 (6.4-49) according to the help dialog.

Unfortunately we tried a lot of things but didn't find a reliable way to reproduce it. We also tried different documents from our LMS, locally generated and even sample files from the internet and they all have a chance to run into this issue. We tested editing the same file with multiple people and while some could save it, for others nothing happened and the error appeared in the logs.

The error isn't saying too much about what exactly went wrong so I'm not sure what additional information I could provide that are helpful. If there is anything I can provide please let me know.
Comment 1 Jan Bebendorf 2021-10-31 23:56:37 UTC
Collabora seems to build their docker images with a pretty old version of LibreOffice (6.4). Switching to manual builds with the up 2 date version of LibreOffice solved this issue.
Comment 2 Xisco Faulí 2022-05-03 11:09:54 UTC
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.