Bug 141923 - My expenses1.ods file will not open and I keep getting the Read Format error in my summary.
Summary: My expenses1.ods file will not open and I keep getting the Read Format error ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.0.5.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-26 22:24 UTC by Suzanne
Modified: 2021-12-02 04:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
this has to do with tax expenses (14.06 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-04-26 22:25 UTC, Suzanne
Details
Fixed file (15.81 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-04-27 08:59 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Suzanne 2021-04-26 22:24:09 UTC
Description:
I am very new to Linux. I need help in this problem. (Ubuntu system) LibreOffice calc 7.0.5  file expenses1.ods will not open at all. I get the "Read Error Format error discovered in the file in sub-document content.xml at 2,65084(row,col)" when I try to open the file.
LibreOffice has never crashed before. 


Steps to Reproduce:
1.found the file
2.opened the file
3.read error format error discovered in the file in sub-document contnent.xml at 2,65084(row,col)

Actual Results:
I do not know how to fix this problem at all.

Expected Results:
That the file would open like it normally did before


Reproducible: Didn't try


User Profile Reset: No



Additional Info:
I need help with this
Comment 1 Suzanne 2021-04-26 22:25:21 UTC
Created attachment 171435 [details]
this has to do with tax expenses
Comment 2 Harshita Nag 2021-04-27 05:18:38 UTC
Hello Suzanne,

    Thank you for reporting the bug. Can you see if bug 83836 is similar to your problem so that I can mark your report as a duplicate of it? (Later bugs are generally marked as duplicates of earlier bugs). Bug 83836 seems to be RESOLVED so you can follow the comments over there for resolving your problem or asking any queries.
Comment 3 Julien Nabet 2021-04-27 08:59:46 UTC
Created attachment 171444 [details]
Fixed file

On pc Debian x86-64 with master sources updated today, I reproduced the pb and noticed this log on console:
warn:sc.filter:88599:88599:sc/source/filter/xml/xmlwrap.cxx:217: SAX parse exception caught while importing: com.sun.star.xml.sax.SAXParseException message: [file:///tmp/expenses1.ods line 2]: Opening and ending tag mismatch: table line 0 and table-row-group
 /home/julien/lo/libreoffice/sax/source/fastparser/fastparser.cxx:609
    wrapped: void message: /home/julien/lo/libreoffice/tools/source/debug/debug.cxx:104 PublicId:  SystemId: file:///tmp/expenses1.ods LineNumber: 2 ColumnNumber: 65084

So I renamed the file to a zip file, unzipped it and removed the closing and opening tags "table-row-group".

I must recognize I don't know how they could be added in the file.
Comment 4 Roman Kuznetsov 2021-05-04 14:23:40 UTC
Suzanne, where did you get the file? I mean did you create the file yourself in LibreOffice or you got it from somewhere?
Comment 5 QA Administrators 2021-11-01 04:15:27 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-12-02 04:44:14 UTC
Dear Suzanne,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp