Bug 150083 - FILESAVE ODS Saving modified spreadsheet with File open & File edit password and Shared mode leads to General I/O Error
Summary: FILESAVE ODS Saving modified spreadsheet with File open & File edit password ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Password-Protected
  Show dependency treegraph
 
Reported: 2022-07-21 10:00 UTC by Gabor Kelemen (allotropia)
Modified: 2023-08-25 03:05 UTC (History)
4 users (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 Gabor Kelemen (allotropia) 2022-07-21 10:00:50 UTC
This is a continuation of bug 150044

1, Open attachment 181308 [details] with password "test"
2, Choose Edit - Edit mode 
3, Enter some text in a cell, and choose File - Save

You get a General Error, as seen on attachment 181327 [details]
This does not happen if you choose File - Save As and set open/edit passwords.

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 28daee8a3252e03a67484dc8d3dd26fd73af4826
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: hu-HU (hu_HU.UTF-8); UI: en-US
Calc: threaded

This started to be visible in 5.4, probably with the bug 56173 (file open password +  shared status saved) being fixed - before the save did not do anything.
Since then having file open password + file edit password + shared status gives this error message.
Not a regression, since it was differently bad back then.
Comment 1 raal 2022-07-21 14:39:18 UTC
no repro Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 28daee8a3252e03a67484dc8d3dd26fd73af4826
CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded
Comment 2 Rafael Lima 2022-07-21 18:48:29 UTC
Not repro with

Version: 7.3.4.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.4-0ubuntu0.22.04.1
Calc: threaded

Also not repro with

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 21a31eefab1401d288dbb8220f3df3365be9efaf
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Calc: threaded

I edited and saved the file. No error occurred.
Comment 3 Buovjaga 2023-01-25 13:09:03 UTC
No repro. Gábor: do you still see this?

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4172fcb7514ff8a9e9740ff0939e9a2f611edbce
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 25 January 2023
Comment 4 QA Administrators 2023-07-25 03:16:25 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2023-08-25 03:05:52 UTC
Dear Gabor Kelemen (allotropia),

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