I have loaded Catalina public beta and LibreOffice 220.127.116.11 onto a MacBook Pro 2013, in order to test features I use often. One particular issue has appeared:
In previous MacOs versions, Save-As request from a Writer template document opened a dialog box with the title of the template highlighted, so that pasting the preferred title from a clipboard was possible. Writer would accept the pasted title.
After running Libreoffice in Catalina, the Save-As dialog box opens with the title NOT highlighted. Further, trying to paste the title into the box after selecting the template title does not substitute the clipboard text. In effect, Save-As dialogs do not react to clipboard pasting, and require that you type the title into the box. While not critical, this is a nuisance issue.
If you need documentation, I can deliver it to you upon your need. Realizing Catalina is an unfinished OS, this may be an issue Apple will fix. However, since LO is not used as a standard test of OS compatibility for Apple, it may be ignored.
"Save as" seems to not be working on Catalina with LO6322 or LO6282 either, when using Calc.
See for example, bug 128233
*** Bug 128233 has been marked as a duplicate of this bug. ***
Confirming given bug 128233
I have not Mac, but if through Menu/File/Save a copy, goes, could be a good worgkaround.
Tried that too out of desperation. No go.
Don't see the issue. Save As gives me the usual dialog and at least with Cmd+up it's possible to go up when the target directory is not in the favorite list.
Note that LibreOffice Vanilla does not suffer from this problem.
However, LOVanilla does not support JDBC databases making it useless for any of my configured work databases which use a JDBC driver to access the data.
So I am currently in the situation of having to copy my mailmerge LO6322 Writer output to new document in LOVanilla, and then saving that to disk, saving as PDF, etc. If I didn't have LOVanilla, I'd be stuffed.
(In reply to Heiko Tietze from comment #6)
> Don't see the issue. Save As gives me the usual dialog and at least with
> Cmd+up it's possible to go up when the target directory is not in the
> favorite list.
You are on Catalina, yes ?
I don't even get a Finder dialog when I use the Save as/Export/Save a copy menu or toolbar button.
Also note that "Save as" also works when an existing file is opened, edited and saved.
This smacks of a permissions issue.
Are there several types of authorized developer where only AppleStore approved apps get to function fully ?
(In reply to Alex Thurgood from comment #9)
> You are on Catalina, yes ?
Yes, I am (for daily work it's Linux). But prefer to leave this topic for the QA experts as it might be a complex topic. If needed I can test with Vanilla and self-build master.
Me and all my colleagues are facing the exact same problem since we updated to Catalina on different LO versions (5.5, 6.2...)
It seems to be in all dialog box on all LO apps (Writer, Calc...): impossible to use keyboard shortcuts => we used to copy/paste filenames while saving for example => we can still do a right-click/paste but no keyboard shortcut anymore
It is only happening in Dialog boxes.
Other softwares (I tried in Chrome but also Gimp, VLC, Inkscape) are working properly.
It happened to all my colleagues and I when we updated MacOS to Catalina.
If anybody has an idea for a work-around that would be great!
(In reply to fkolmer from comment #12)
> It happened to all my colleagues and I when we updated MacOS to Catalina.
> If anybody has an idea for a work-around that would be great!
Have you tried granting "full disk access" to the LibreOffice.app bundle via the
System Preferences > Security & Confidentiality settings ?
*** Bug 130537 has been marked as a duplicate of this bug. ***
tested on macOS 10.15.3 LO Version: 18.104.22.168.alpha0+
Build ID: 4caa7b790cf99eebbe47fc2e6a56124c42f1f3fc
CPU threads: 4; OS: Mac OS X 10.15.3; UI render: default; VCL: osx;
Locale: de-DE (de_DE.UTF-8); UI-Language: en-US
Shift + Command + S (save as) results in the save dialog with highlighted titel (different than what OP described) but confirming pasting is not possible.
Pasting becomes possible when I use my clipboard manager.
But I think the problem is more general. cmd + A does not select all text, even with the cursor active in the titel field of the save dialog.
Enabling Full Disk Access for LibreOfficeDev app in System Preferences > Security > Privacy does not change this situation. LibreOfficeDev shows up in Files and Folder security settings and al checkboxes are ticked.
This is a bummer.
In my case, it's show save as dialog with highlighted title, but can't paste in it.
Build ID: 15c0f22c31a46ce37e98f9394e6a8e0bc92495f9
CPU threads: 8; OS: Mac OS X 10.15.3; UI render: default; VCL: osx;
Locale: en-ID (en_ID.UTF-8); UI-Language: en-US
*** Bug 131103 has been marked as a duplicate of this bug. ***
I see exactly the same bug on a MacBook Air running macOS Catalina with LibreOffice 22.214.171.124:
- Click “save as” – the spinning rainbow wheel appears for ~2 seconds, but *no* file dialogue opens.
- Click “open” an other document – spinning wheel again, no dialogue.
In the preferences, I enabled the LibreOffice dialogues instead of the
natives ones. Now all file operations worked again (but these dialogues are
somewhat clumsy compared to the macOS native ones). Changed the preferences
back to the native dialogues – same effect as above, no file dialogues, just the
After restarting LibreOffice, the native dialogues work again (but I didn't make a statistics iff and how often the bug appears again).
*** Bug 131292 has been marked as a duplicate of this bug. ***
The issues described by the original bug reporter is that pasting into the name field "Save as" when saving doesn't work. This is of course not a showstopper, but annoying.
It may be related to the code-signing issues in bug 126409, but hard to say.
A few of the comments relate to another bug, that if you use a non-admin account (standard account) or install a language pack, you need to grant Full Disk Access
That is filed as bug 128233
I'm lowering the importance of this bug to the default and changing the summary to reflect the original issue
*** Bug 133707 has been marked as a duplicate of this bug. ***
*** Bug 134718 has been marked as a duplicate of this bug. ***
*** Bug 134446 has been marked as a duplicate of this bug. ***