Bug 145633 - Format Error
Summary: Format Error
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-11 19:54 UTC by boiraroya
Modified: 2022-09-05 03:38 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 boiraroya 2021-11-11 19:54:55 UTC
Error. "Read Error.
Format error discovered in the file in sub-document content.xml at 2,261580(row,col)."

Open libreoffice document in google drive whit Cloud Mounter.
after opening it gives the error.

Corrupts content.xml
Comment 1 Julien Nabet 2021-11-12 13:10:33 UTC
I don't know if the file would need sanitizing (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission) but without attaching the corrupted document, it won't be easy to help.
Comment 2 eisa01 2022-02-05 15:53:37 UTC
Please upload a sample file that exhibits the issue
Comment 3 QA Administrators 2022-08-05 03:32:29 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2022-09-05 03:38:52 UTC
Dear boiraroya,

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