Description: "The lock file could not be created for exclusive access by LibreOffice, due to missing permission to create a lock file on that file location or lack of free disk space." It would be good to know what the update is on fixing the lock file issue when trying to open attachments to Mac Mail. Currently it can be resolved by copying the file rather than saving it in the read only mode - but it's still a pain. Steps to Reproduce: 1.Click on the Attachment in a Mac Mail message, or 2.Save the attachment to a folder 3. Actual Results: "The lock file could not be created for exclusive access by LibreOffice, due to missing permission to create a lock file on that file location or lack of free disk space." message Expected Results: A fully read/write document Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (Catalina) OS is 64bit: yes
Hi Bob, Thank you for reporting the bug. I can confirm that the bug is present in master. Version: 6.4.0.0.alpha1+ Build ID: d2b5ab3498a78c6d164a15b3bf2b947553ea2743 CPU threads: 8; OS: Mac OS X 10.15; UI render: default; VCL: osx; Locale: en-ID (en_ID.UTF-8); UI-Language: en-US Calc: threaded
@Alex, do you reproduce this issue ?
(In reply to Xisco Faulí from comment #2) > @Alex, do you reproduce this issue ? I never use Mac Mail.app as IMHO it is a pile of security-hole ridden sh** Unable to test, sorry. The lock file message is probably Catalina's way of telling you that LO is trying to step outside of the allowed jail (secure container) in which apps are now supposed to run. LO creates a lock file (hidden file) of the file to be modified when you load it into memory for the purposes of file recovery in the event of a crash. I'm guessing that LO is attempting to create this lock file in a directory that is now forbidden by Catalina's security policy.
So, set up a test account on Mail.app and sent myself an ODT from a different account. Confirming the reported behaviour with Version: 6.3.1.2 Build ID: b79626edf0065ac373bd1df5c28bd630b4424273 Threads CPU : 4; OS : Mac OS X 10.15.1; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded Screenshot of message that is displayed attached.
Created attachment 155572 [details] Error message displayed when opening attachment in Mail.app
FWIW, this does not happen on macOS 10.14.6 with the same version of LO(6312), so this behaviour is new with Catalina.
The bug is resolved if you open Privacy Settings and add LibreOffice to "Allow Full Disk Access"
Hm.. I guess this sounds like a pretty serious drawback, if you can't open attachments directly from Mail? I'm bumping the importance Workaround to grant full disk access
Granting full access is a workaround, but it would be much better if that was not needed. Note that according to the initial bug description, it is the lock file that can't be created. Presumably the file where the actual attached document has been stored by Mail.app has been opened just fine by LibreOffice. So what is needed is some tweaks to make LibreOffice not care if it can't create a lock file, especially if the lock file would be created in some location that can be recognised as "special". Will investigate.
For me, using LibreOffice 6.4.3.2, the "Document Could Not Be Locked" dialog offers the possibility to open the document read-only, which makes sense. (What would it even mean to be editing a document that is actually an attachment to an email message? You wouldn't be modifying the attachment even if you would make changes and save them. You would just pointlessly be modifying a temporary file created by Mail.app) which is a preferable workaround than granting full access, don't you think? If you then do a File > Save As, the document can be edited normally. Would an acceptable fix be to simply get rid of the "Document Could Not Be Locked" dialog, and instead just open the document read-only? Bob, if your "Expected Result" is "A fully read/write document", where would that document be stored? Note that the attachment that Mail.app writes to disk is in a scratch location, like /Users/tml/Library/Containers/com.apple.mail/Data/Library/Mail Downloads/DF2EC83C-48C4-4E39-9D56-5FC036385737/AAA1.odt . That folder is not one the users is supposed to be poking into.
(Removed the "full disk access workaround" from the bug summary; this has nothing to do with full disk.)
Maybe instead of showing the dialog, we should just open the document read-only, and the blue "This document is open in read-only mode" notification bar could be made more verbose, perhaps adding something like "If you want to make changes to it, you first need to save it to a folder you have write access to."
Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6c102b0a12ed911b207d8b1da421f2b916c2bcdf tdf#128526: Make the read-only notification a bit more verbose It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Alex Thurgood from comment #3) > (In reply to Xisco Faulí from comment #2) > > @Alex, do you reproduce this issue ? > > I never use Mac Mail.app as IMHO it is a pile of security-hole ridden sh** > > Unable to test, sorry. > > The lock file message is probably Catalina's way of telling you that LO is > trying to step outside of the allowed jail (secure container) in which apps > are now supposed to run. LO creates a lock file (hidden file) of the file to > be modified when you load it into memory for the purposes of file recovery > in the event of a crash. I'm guessing that LO is attempting to create this > lock file in a directory that is now forbidden by Catalina's security policy. This happened to me also when I tried to open several files in Mojave, which I installed only yesterday on my MacBook Pro. Is there some way to disable all this without doing some fancy maneuvers? The files opened just fine before yesterday, and though I know enough about my Mac to handle things, generally, I don't understand other than straightforward instructions for technology, need steps of actions and no scary stuff. (I know I sound like an idiot, but I want to be plain about what kinds of instructions you can send me and expect me to succeed in following them.) I'm very dismayed. This never happened to me before; I am the only one using the files (not attachments, nor Apple Mail messages but I must open those also), so I shouldn't have to get permission to open them; I don't want to lock anything; and I don't want read/write only nor to have to copy any file that no longer works. Is there something I can do? I'm wishing now that I had never gone to LibreOffice. I have so many .odt files now, so if they won't open, I'll be stuck. I hope you can help me.
Janedicker, are you saying that your comment has nothing to do with opening attachments in the Mail app? If so, then your comment is only confusing matters in this bug report, sorry. Please file a *separate* bug report for your issue, describing in as much detail as you can what you were doing and what happened. Thanks.
Samuel Mehrbrodt committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/69e3b647d27d4fdb8243d6cca86f9287a5be6026 Revert "tdf#128526: Make the read-only notification a bit more verbose" It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Samuel Mehrbrodt committed a patch related to this issue. It has been pushed to "libreoffice-7-0": https://git.libreoffice.org/core/commit/9d86d44665a7cc6ecd636fd2b7a817083497d2f8 Revert "tdf#128526: Make the read-only notification a bit more verbose" It will be available in 7.0.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Dear bob, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I just encountered the bug after updating to the latest version. It occurs while trying to open files, not mails (haven't tried). There is more than enought space on the disk, other windows apps manage to create files. Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL
(In reply to reply22.upm9n from comment #19) Please don't update this report's fields to only match your configuration. I've set them back to the earliest version affected, and macOS. Let's keep this report as macOS-only. You will likely find other reports for Windows that match your issue better.