When I set a different user profile via "--env:UserInstallation=file:///tmp/test" I get a fatal error saying, that the user based installation could not be completed.
The problem only exists when LibreOffice gets installed from the Mac App Store.
If I download the excact same version from the official website instead then the error disappears.
If've tested on macOS Ventura 13.2.1 on multiple Macs (arm64) with LibreOffice version 188.8.131.52.
Giving LibreOffice Full Disk Access has no effekt either.
I also tried to user a different profile path under $HOME without success.
Steps to Reproduce:
1. Download LibreOffice from Mac App Store
2. Run this command: "/Applications/LibreOffice.app/Contents/MacOS/soffice "-env:UserInstallation=file:///tmp/test"
Fatal Error: The application could not be started because the user-based installation could not be completed (translated from german error message).
LibreOffice should not produce a fatal error.
User Profile Reset: Yes
Background: we're using LibreOffice to convert PDFs from templates running --headless which requires to set a different user profile in case another LO process is already running.
Created attachment 185726 [details]
Screenshot of error message (locale: DE)
Macs with Intel processor (x86-64) are also affected by this bug.
- iMac Retina 4K, 21,5", 2019 with 3,6 GHz Quad-Core Intel Core i3
- macOS Ventura 13.2.1
- LibreOffice 7.4.6002 from Mac App Store
Here is the english error message:
$ /Applications/LibreOffice.app/Contents/MacOS/soffice "-env:UserInstallation=file:///tmp/test"
LibreOffice 7.4 - Fatal Error: The application cannot be started.
User installation could not be completed.
Created attachment 186310 [details]
Screenshot of error message (locale: EN)
Running LO with the open command produces the error as well:
$ open -a LibreOffice.app --args -env:UserInstallation=file:///tmp/test
Also both standard and admin users experience this problem.
Version: 184.108.40.206 / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 8; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR
from the Apple appstore.
At a guess, probably due to the sandboxing requirement, in which case, don't expect a solution any time soon, or rather expect that this bug will be closed as NOTABUG.
I hope that it isn't due to the sandboxing requirement, and that it can be resolved to work in the same way as the non-appstore version, but as I'm not a dev familiar with the build requirements for releasing to the appstore, who knows?
The appstore version is currently too crippled to be of any use in situations like this.
Marking as regression because it works in the TDF download version.
Someone more knowledgable of the intricacies can correct my assessment as appropriate.
(In reply to Alex Thurgood from comment #7)
> Marking as regression because it works in the TDF download version.
> Someone more knowledgable of the intricacies can correct my assessment as
if it happens in the Mac App Store version but not in the TDF it doesn't mean it's a regression, it means it's a Mac App Store issue only. Removing keywords