Bug 112461 - Cannot open certain ODG documents; Read Error; Format Error
Summary: Cannot open certain ODG documents; Read Error; Format Error
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: Other macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-18 04:37 UTC by Neil Zimmerman
Modified: 2019-01-03 22:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot of error (3.31 MB, image/jpeg)
2017-09-18 04:42 UTC, Neil Zimmerman
Details
This one is the one modified using the zip/xml technique (57.68 KB, application/vnd.oasis.opendocument.presentation)
2018-01-10 16:49 UTC, César Biosca.
Details
This is the original file after copying the content from LibreOffice Draw (58.48 KB, application/vnd.oasis.opendocument.presentation)
2018-01-10 16:52 UTC, César Biosca.
Details
Repaired file (61.23 KB, application/vnd.oasis.opendocument.presentation)
2019-01-03 22:29 UTC, Regina Henschel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Neil Zimmerman 2017-09-18 04:37:44 UTC
Description:
All ODG documents created with v 5.4.1 or 5.3.6 will not open. Trying to open files results in error: "Read Error. Format error discovered in the file in sub-document content.xml at position 2,4256(row,col)."

Steps to Reproduce:
1.Open Libre Office
2.When presented with Recent Files thumbnails, click on a thumbnail to open document

Actual Results:  
Document does not open. Window appears with error: "Read Error. Format error discovered in the file in sub-document content.xml at position 2,4256(row,col)."

Expected Results:
Open the document.


Reproducible: Always

User Profile Reset: No

Additional Info:
Opened Libre Office in Safe Mode. Problem not resolved. Attempting to open documents yielded same result.


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Comment 1 Neil Zimmerman 2017-09-18 04:42:03 UTC
Created attachment 136329 [details]
screenshot of error
Comment 2 Alex Thurgood 2017-09-18 07:03:32 UTC
@Neil : no repro with 

Version: 5.4.1.2
Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527
CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; 
Locale: fr-FR (fr_FR.UTF-8); Calc: group

when attempting to open a simple ODG file made in LO536 containing some of the pre-made shapes from the draw objects menu.

We need more information, and preferably a document that shows the issue or detailed steps as to what the ODG file contains.
Comment 3 Alex Thurgood 2017-10-12 07:25:45 UTC
@Neil : the XML error you report indicates that the file was somehow corrupted when it was saved, or at least when its last state before some catastrophic event (power outage, dodgy RAM, LO crash, etc) was saved from memory to disk or to a remote file share.

What were the specific conditions under which these ODG files were saved ?
- network / cloud save ?
- USB key or external storage save ?


If you unzip the ODG file and examine the content.xml file at the line and point indicated in the error message, what do you see ?
Comment 4 César Biosca. 2018-01-10 16:49:59 UTC
Created attachment 139022 [details]
This one is the one modified using the zip/xml technique

This one is the one modified using the zip/xml technique
Comment 5 César Biosca. 2018-01-10 16:52:17 UTC
Created attachment 139023 [details]
This is the original file after copying the content from LibreOffice Draw

This is the original file after copying the content from LibreOffice Draw
Comment 6 César Biosca. 2018-01-10 16:53:20 UTC
Hope that both attachments would be helpfull.
Comment 7 Alex Thurgood 2018-02-13 13:25:55 UTC
(In reply to César Biosca. from comment #5)
> Created attachment 139023 [details]
> This is the original file after copying the content from LibreOffice Draw
> 
> This is the original file after copying the content from LibreOffice Draw


This file refuses to open for me in

Version: 5.4.5.1
Build ID: 79c9829dd5d8054ec39a82dc51cd9eff340dbee8
Threads CPU : 4; OS : Mac OS X 10.13.3; UI Render : par défaut; 
Locale : fr-FR (fr_FR.UTF-8); Calc: group

I just get a grey document window in which the file attempts to load, and this then disappears without any error message.


If I try to open the same file in 
Version: 5.3.7.2
Build ID: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059
Threads CPU : 4; Version de l'OS :Mac OS X 10.13.3; UI Render : par défaut; Moteur de mise en page : nouveau; 
Locale : fr-FR (fr_FR.UTF-8); Calc: group

I get the following message :

Erreur de lecture.
Erreur de format dans le fichier du sous-document content.xml à la position 2,4174(row,col).
Comment 8 Alex Thurgood 2018-02-13 13:32:57 UTC
I get the same error message in LO330, so the problem lies with the particular ODT document and not LibreOffice in general.

Something you have done, or something which has happened to your computer, has caused this file to become corrupt. The way to fix that is to unzip the file and correct it at the location indicated in the error message.

Several possible reasons are known that might cause these problems:

- reading/writing to a USB or external disk - from my own experience, MacOS isn't very reliable at maintaining multiple USB connected storage devices correctly and will sometimes disconnect them for no apparent reason

- reading/writing to a network storage that suddenly goes offline (e.g. power cut, network connection down, etc)

Whatever the case, the files have been corrupted. In theory, they can be repaired by correcting/removing the additional XML tags that have been inserted erroneously.
Comment 9 Regina Henschel 2019-01-03 22:29:10 UTC
Created attachment 147980 [details]
Repaired file

The original file is corrupt. It has parts '="nonzero"' where it should be 'svg:fill-rule="nonzero"'. I have repaired that.

I think, that there is no error in LibreOffice and the issue should be closed. In case a reproducible way to create such damaged file is found, it can be reopened.