Bug 216685

Summary:	Unexpected read-only mode behaviour for saving and editing
Product:	[Applications] calligrasheets	Reporter:	kde
Component:	general	Assignee:	Calligra Sheets (KSpread) Bugs <calligra-sheets-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	2.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description kde 2009-11-29 17:30:33 UTC

Version:           2.1.0 (using KDE 4.3.3)
OS:                Linux
Installed from:    Ubuntu Packages

When opening a document right from the web with Firefox, without saving it first, or when running chmod -w on a spreadsheet the resulting file is opened as read-only/write-protected, as expected.

If the file is then saved locally with "Save As" it stays write-proteted, "Reload" does not help either. It's necessary to open the document again for the document to be editable as normal.

However, even though the QRubberBand for resizing a column does not appear while having a document open as read-only, it's still possible to resize a column with the toolbar option Format>Column>Resize column. This incidentally also removes the  '(write protected)'  from the title but the column handlers and other sheet options are still blocked.

Several other operations like Insert are also not blocked from the toolbar and remove the notification from the title.

Comment 1 Andrew Crouthamel 2018-11-09 01:07:37 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Andrew Crouthamel 2018-11-20 04:08:58 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Justin Zobel 2023-01-02 02:04:09 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2023-01-17 05:14:11 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2023-02-01 05:03:51 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!