Budget 2020 proposals and macOS Catalina support / onboarding

[Eivind Samseth]

Hello,
I see there is a proposal for the budget 2020 to fix the macOS 10.15 notarization, and the longstanding issues in the ESC calls about fixing this bug and a save as behavior bug https://wiki.documentfoundation.org/Development/Budget2020#Fix_macOS_10.15_notarization <https://wiki.documentfoundation.org/Development/Budget2020#Fix_macOS_10.15_notarization>

That is probably a very good idea to fix, as there’s been many bug reports about people being unable to save on Catalina.

I installed my old SSD on my MBP to test Catalina and these issues, and this is what I found:
 * An admin user has no problem to install LibreOffice, open the app, and save
 * A standard user (default for the non-main account) will not be able to save files, without granting “Full Disk Access”: https://bugs.documentfoundation.org/show_bug.cgi?id=128233 <https://bugs.documentfoundation.org/show_bug.cgi?id=128233>
 * An admin user installing a language pack will not be able to save files, without granting “ Full Disk Access”: https://bugs.documentfoundation.org/show_bug.cgi?id=132025 <https://bugs.documentfoundation.org/show_bug.cgi?id=132025>
 * The save as bug being tracked in the ESC is actually not a serious bug, just not being able to paste in the file name field. The two above should be tracked instead, and not https://bugs.documentfoundation.org/show_bug.cgi?id=126638 <https://bugs.documentfoundation.org/show_bug.cgi?id=126638>

As such, many new users to LO will be unable to get the program to work as they either are on a Standard account or are installing another language

I suggest that the install page should be changed to include instructions to grant “Full Disk Access” in System Preferences -> Security and Privacy -> Privacy
This will help many users that currently have to google, use the ask portal, or give up if they’re not technically inclined

I don’t know, but it could be possible, that these save as bugs are related to the code signing / notarization issue, but I’m not a macOS developer.

The current code signing has also become more broken since Cloph looked at the issue last fall, as now the LibreOfficePython.framework reports modified files (all in various __pycache__ folders)

Best,
Eivind
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20200411/df1a9ad7/attachment.htm>