Bug 118447 - ~.lock problem
Summary: ~.lock problem
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.6.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-29 10:57 UTC by richard@darton-moore.co.uk
Modified: 2018-07-03 08:37 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Writer doc created using label format. (10.65 KB, application/vnd.oasis.opendocument.text)
2018-06-29 15:53 UTC, richard@darton-moore.co.uk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description richard@darton-moore.co.uk 2018-06-29 10:57:39 UTC
I have a file set up as labels.  The labels are not prefilled as in mail merge. I fill them in as required.  It is no longer possible to edit the file as it opens as read-only.

I have tried deleting the ~.lock file but it persists.  I have copied the file from my Dropbox folder to my hard disk and then tried to delete the lock file but still it persists.
Comment 1 Dieter 2018-06-29 11:16:35 UTC
Hi Richard, I'm not sure, if you want to report a bug or if you are searching for help. In the letter case you should use the support at http://ask.libreoffice.org/en/questions/ If you want to report a bug, some informations are needed (steps to reproduce or an example file).
Comment 2 richard@darton-moore.co.uk 2018-06-29 11:58:14 UTC
I'm sorry Dieter.  I'd thought that the steps were self evident.

1. Open the document to edit
2. Find that it cannot be edited and that the status information at the foot of the screen says 'read-only'
3. Close the file
4. Delete the ~.lock file as suggested in community forums
5. Re-open the file (same result as 2. above)
6. Move the file from Dropbox as suggested in community forumw
7. Repeat steps 1 to 5 above but the with the same 'read-only' result.

I think that I have exhausted all the Linux based community responses and therefore have concluded that this is a bug.

I hope that helps.  Thanks for looking at this.
Comment 3 Julien Nabet 2018-06-29 14:33:32 UTC
Would it be possible you attach the file or does it contain private/confidential part?
Indeed, without the file to test, we can't give it a try.

BTW, 5.1.6 is quite an old version, could you give a try to last stable LO release 6.0.5?
Comment 4 richard@darton-moore.co.uk 2018-06-29 15:53:55 UTC
Created attachment 143209 [details]
Writer doc created using label format.
Comment 5 richard@darton-moore.co.uk 2018-06-29 15:56:43 UTC
Ah.  My comments were deleted.  Didn't realise that they had to be entered with the file upload.

I am using the older version of LO as that is the current version available through Mint 18.3

This file has opened OK in the past so I don't think that it's a problem of an older LO version.

This version was created using the new labels option. All other LO documents (of all types open OK in editable mode whether shared with MS users or Mac users, and whether in native format or not.

Thanks for looking into this.
Comment 6 Julien Nabet 2018-06-29 19:16:30 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce the problem.
I got a message indicating "Write-protected content cannot be changed"
Comment 7 Julien Nabet 2018-06-29 19:56:34 UTC
I found how to put unlock this.
- select a frame (you'll see blue points around the rectangle corresponding to a label)
- right click "Properties"
- Select "Options" tab
- in "Protect" part at left, uncheck "Contents" checkbox
- click Ok

It'll apply automatically at all the labels.
Comment 8 richard@darton-moore.co.uk 2018-07-03 08:21:35 UTC
Thank you Julian.

I had tried that but on the inner frame in the top left label.  No options were available to change.  I've realised that this was because the outer frame was protected.

Thanks for your perseverance.
Comment 9 Julien Nabet 2018-07-03 08:37:03 UTC
Thank you for your feedback Richard.
Let's put this one to WFM since there was no need for a fix.