<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Catalina: Can't open attachments in Mail due to Lock File issues (full disk access workaround)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128526#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Catalina: Can't open attachments in Mail due to Lock File issues (full disk access workaround)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128526">bug 128526</a> from <a class="email" href="mailto:tml@iki.fi" title="Tor Lillqvist <tml@iki.fi>"> Tor Lillqvist</a> <pre>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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>