Bug 134703 - Cannot save spreadsheet on Libreoffice-calc 7.0
Summary: Cannot save spreadsheet on Libreoffice-calc 7.0
Status: RESOLVED DUPLICATE of bug 134332
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) rc
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2020-07-09 21:43 UTC by Kevin Donovan
Modified: 2020-07-10 20:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Donovan 2020-07-09 21:43:14 UTC
I edited a spreadsheet on Libreoffice 7.0.  When I try to save it, I get an error message (Input Output error), and the changes are not saved.

Steps to Reproduce:
1. Open the spreadsheet.
2. Modify one or more cells.
3. Press the save button.

Actual Results:
Error message.  Changes are not saved.

Expected Results:
Spreadsheet is saved, with the changes.

Reproducible: Always

User Profile Reset: Yes

Additional Info:
This is an encrypted spreadsheet, and has 7 sheets.  As a test, I created a new spreadsheet, not encryped.  I filled in a few cells.  I was able to save it, even after editing it.

I also running in Safe Mode, but it did not fix the problem.

Build ID: 00(Build:1)
CPU threads: 16; OS: Linux 5.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.utf8); UI: en-US
Debian package version: 1:7.0.0_rc1-5
Calc: threaded
Comment 1 Xisco Faulí 2020-07-10 13:14:40 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 Telesto 2020-07-10 20:59:37 UTC

*** This bug has been marked as a duplicate of bug 134332 ***