Bug 123501 - Saved xlsx file, LibreOffice crashed, now file is corrupted
Summary: Saved xlsx file, LibreOffice crashed, now file is corrupted
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: XLSX
  Show dependency treegraph
Reported: 2019-02-16 16:27 UTC by icemanjunk
Modified: 2019-10-22 02:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description icemanjunk 2019-02-16 16:27:38 UTC
Saved xlsx file, LibreOffice crashed, now file is corrupted

Actual Results:
you open the file, it cant be repaired, end of story

Expected Results:
dont corrupt my work!

Reproducible: Always

User Profile Reset: No

Additional Info:
Comment 1 m.a.riosv 2019-02-16 22:09:05 UTC
Please attach a sample file with such issue.

Have you tested with Menu/Help/Restart in Safe <Mode
Comment 2 QA Administrators 2019-09-21 03:08:07 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-10-22 02:33:09 UTC
Dear icemanjunk,

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