Bug 111554 - FILEOPEN Format error on 5.4.0.3, but opens fine on the same machine with 5.3.5-1 (Arch Linux)
Summary: FILEOPEN Format error on 5.4.0.3, but opens fine on the same machine with 5....
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks:
 
Reported: 2017-08-09 13:21 UTC by Artem
Modified: 2017-09-14 10:23 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
file-in-question (47.62 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-08-09 13:21 UTC, Artem
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Artem 2017-08-09 13:21:08 UTC
Created attachment 135342 [details]
file-in-question

Steps to reproduce: open the ods file

Expected behaviour: file opens without the error prompts

Actual behaviour: when opening with libreoffice-fresh (5.4.0.3) i get an error message "Read Error. Format error discovered in the file in sub-document content.xml at 2,87813(row,col)." When opening with libreoffice-still (5.3.5.2 30m0(Build:2)) on the same PC (removing fresh, installing still) i get no error prompt

Details:

File was created on the same machine with the same Libreoffice 5.4.0.3. Today i run upon this error. I did  transfer it earlier to my android device with android-file-transfer but i didn't see any indication of it being corrupted in the process. And it opens fine on android with MobySystems Office suite.

If i'm tracing it right, 2,87813 in content.xml is a letter t in a first word table-cell in a part of the file I provided  below (so the 8th symbol in that given part of the file). 

<table:table-cell office:value-type="string" calcext:value-type="string"><text:p>说明</text:p></table:table-cell><table:table-cell office:value-type="string" calcext:value-type="string"><text:p>shuōmíng</text:p><text:p>

In the attachments section there's the ods file itself.

It opens fine on Windows 8.1 with LO 5.2.0.4 ID: 066b007f5ebcc236395c7d282ba488bca6720265

5.4.0.3 also opens just fine the xls file i got by saving the original ods file as xls on that windows machine.

Other ods files open fine, no problems encountered.

My system: 4.12.4-1-ARCH #1 SMP PREEMPT Fri Jul 28 18:54:18 UTC 2017 x86_64 GNU/Linux

LibreOffice 5.4.0.3 40m0(Build:3)

Thanks!
Comment 1 Buovjaga 2017-08-09 13:41:57 UTC
Repro.

Opens fine on 3.6.

Arch Linux 64-bit, KDE Plasma 5
Version: 6.0.0.0.alpha0+
Build ID: 7915f35d7fca5d0720d96954beaa97c00a2c3821
CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on August 7th 2017

Arch Linux 64-bit, KDE Plasma 5
Version: 5.4.0.3
Build ID: 5.4.0-1
CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group

Arch Linux 64-bit
Version 3.6.7.2 (Build ID: e183d5b)
Comment 2 Julien Nabet 2017-08-09 15:11:21 UTC
If you save your ods file into fods with 5.3.5.2, do you reproduce the problem with 5.4.0.3?
If yes, it may give more info since fods is a xml text file with several lines.
Comment 4 Artem 2017-08-09 21:59:50 UTC
(In reply to m.a.riosv from comment #3)
> Please take a look to this thread on Ask.
> 
> https://ask.libreoffice.org/en/question/34411/i-can-not-open-my-spreadsheet-
> it-comes-up-with-this-error-read-error-format-error-discovered-in-the-file-
> in-sub-document-contentxml-at-272157rowcol/

i did take a brief look at this thread before reporting. The thing that stroke me as being different is it failing to open in one version, but having no problems in another version.
Comment 5 Artem 2017-08-09 22:01:26 UTC
(In reply to Julien Nabet from comment #2)
> If you save your ods file into fods with 5.3.5.2, do you reproduce the
> problem with 5.4.0.3?
> If yes, it may give more info since fods is a xml text file with several
> lines.

did that! saved into fods with 5.3.5.2, that fods opened just fine with 5.4.0.3
Comment 6 Julien Nabet 2017-08-10 19:34:04 UTC
On pc Debian x86-64 with master sources updated today (with rendering kde4 and gtk3), I don't reproduce this.
I also tried with LO Debian 5.4.0.3, no pb too.

Just for info, I noticed this:
warn:sc:22420:1:sc/source/filter/orcus/orcusfiltersimpl.cxx:173: Unable to load styles from xml file! failed to load
but perhaps unrelated.
Comment 7 Julien Nabet 2017-08-10 19:37:20 UTC
I just wonder if the zip compression could be a bit corrupted.
Here's the result of zip -v on the file:
zip -v osm1.ods 
	zip warning: undefined bits used in flags = 0x0808: meta.xml
	zip warning: undefined bits used in flags = 0x0808: styles.xml
	zip warning: undefined bits used in flags = 0x0808: manifest.rdf
	zip warning: undefined bits used in flags = 0x0808: settings.xml
	zip warning: undefined bits used in flags = 0x0808: META-INF/manifest.xml
	zip warning: undefined bits used in flags = 0x0808: content.xml

Perhaps the transfer with Android is the cause?
Comment 8 Artem 2017-08-10 22:16:34 UTC
(In reply to Julien Nabet from comment #6)
> On pc Debian x86-64 with master sources updated today (with rendering kde4
> and gtk3), I don't reproduce this.
> I also tried with LO Debian 5.4.0.3, no pb too.
> 
> Just for info, I noticed this:
> warn:sc:22420:1:sc/source/filter/orcus/orcusfiltersimpl.cxx:173: Unable to
> load styles from xml file! failed to load
> but perhaps unrelated.

So maybe not an upstream, but somehow a distro-related thing? if i get it right Buovjaga was able to reproduce it on Arch as well
Comment 9 Artem 2017-08-10 22:50:53 UTC
(In reply to Julien Nabet from comment #7)
> I just wonder if the zip compression could be a bit corrupted.
> Here's the result of zip -v on the file:
> zip -v osm1.ods 
> 	zip warning: undefined bits used in flags = 0x0808: meta.xml
> 	zip warning: undefined bits used in flags = 0x0808: styles.xml
> 	zip warning: undefined bits used in flags = 0x0808: manifest.rdf
> 	zip warning: undefined bits used in flags = 0x0808: settings.xml
> 	zip warning: undefined bits used in flags = 0x0808: META-INF/manifest.xml
> 	zip warning: undefined bits used in flags = 0x0808: content.xml
> 
> Perhaps the transfer with Android is the cause?

i don't think i've experienced any corruptions lately, but you never know...

I've just tried to transfer that original ods back to pc, and it opens fine with  5.3.5.2.
Comment 10 Artem 2017-08-11 01:07:15 UTC
Opened fine on 5.4 on Windows as well. I guess i'll go about leaving a note on an arch bugtracker then.
Once again thanks everyone for your time and efforts
Comment 11 Buovjaga 2017-08-11 07:37:46 UTC
Artem: do you have a copy of the file from before it was transferred to Android?
Comment 12 Artem 2017-08-11 08:30:32 UTC
(In reply to Buovjaga from comment #11)
> Artem: do you have a copy of the file from before it was transferred to
> Android?

no, i'm affraid i don't.
Comment 13 Artem 2017-08-11 08:41:42 UTC
(In reply to Artem from comment #12)
> (In reply to Buovjaga from comment #11)
> > Artem: do you have a copy of the file from before it was transferred to
> > Android?
> 
> no, i'm affraid i don't.

but there were also a few other files i transfered that time: plain text document as well as couple more ods files, and they all open fine in libreoffice-fresh. i could attach them if it would be of any help.
Comment 14 Xisco Faulí 2017-08-11 20:28:03 UTC
Is it an arch problem then ?
Comment 15 Buovjaga 2017-08-12 11:21:42 UTC
(In reply to Julien Nabet from comment #7)
> I just wonder if the zip compression could be a bit corrupted.
> Here's the result of zip -v on the file:
> zip -v osm1.ods 
> 	zip warning: undefined bits used in flags = 0x0808: meta.xml
> 	zip warning: undefined bits used in flags = 0x0808: styles.xml
> 	zip warning: undefined bits used in flags = 0x0808: manifest.rdf
> 	zip warning: undefined bits used in flags = 0x0808: settings.xml
> 	zip warning: undefined bits used in flags = 0x0808: META-INF/manifest.xml
> 	zip warning: undefined bits used in flags = 0x0808: content.xml
> 
> Perhaps the transfer with Android is the cause?

Same warnings are mentioned in this article, which has steps to replace content.xml inside the odf zip: https://softsolder.com/2010/07/25/
Comment 16 Buovjaga 2017-08-12 11:24:57 UTC
It opens fine with LibO AppImage under Arch.

http://libreoffice.soluzioniopen.com/index.php/daily-version/
Version: 6.0.0.0.alpha0+
Build ID: 368b583b992f2e9cad46c2362c9529a07c36d7a9
CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-08-10_02:55:46
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Comment 17 Artem 2017-08-12 12:13:58 UTC
(In reply to Buovjaga from comment #16)
> It opens fine with LibO AppImage under Arch.
> 
> http://libreoffice.soluzioniopen.com/index.php/daily-version/
> Version: 6.0.0.0.alpha0+
> Build ID: 368b583b992f2e9cad46c2362c9529a07c36d7a9
> CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; 
> TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time:
> 2017-08-10_02:55:46
> Locale: fi-FI (fi_FI.UTF-8); Calc: group

Confirm that on my end! Opened fine with that AppImage. In fact it also opened fine with LibreOffice-5.4.0.standard-x86_64.AppImage (304.54 MB)
Comment 18 Artem 2017-09-14 10:21:40 UTC
fixed for me with LibreOffice 5.4.0.3 40m0(Build:3)!
link to the now closed bug on arch tracker: https://bugs.archlinux.org/task/55103
thanks!