Bug 128171 - macOS langpack install script no longer finds parallel LO installations - Catalina 10.15
Summary: macOS langpack install script no longer finds parallel LO installations - Cat...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
6.3.2.2 release
Hardware: All macOS (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-16 08:54 UTC by Alex Thurgood
Modified: 2019-11-26 07:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Thurgood 2019-10-16 08:54:17 UTC
Description:
Attempting to install a FR langpack for LO6322, which has been installed in parallel to LO627

Name of application bundle in Applications folder :
LibreOffice (for LO627)
LO6322 (for LO6322)

Attempting to install the langpack for LO6322 fails because the secondary, or further LO installations are not found. Consequently, no dialog is displayed allowing the user to choose which bundle to install the langpack to.

The osx_install.applescript file is failing to find the other installations.

Attempting to install the LO6322 langpack then fails with:
/Applications/LibreOffice.app This is not a valid installation of LibreOffice 6.3




Steps to Reproduce:
See above description

Actual Results:
Installation fails to find other, parallel installations of LO. Script then fails to install langpack.

Expected Results:
The script should correctly find the other installations, and allow the user to choose the existing installation into which the langpack contents should be copied.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Comment 1 Alex Thurgood 2019-10-16 08:56:17 UTC
The reason for the script failure is possibly linked to Apple's new directory security settings which require a user to authenticate by default whenever an external app wants access to the protected directory.
Comment 2 Alex Thurgood 2019-10-16 10:05:24 UTC
Taking this from the applescript :

mdfind "kMDItemContentType == 'com.apple.application-bundle' && kMDItemDisplayName == 'LibreOffice*'"


gives:

/Applications/LibreOffice.app

so the script only finds bundles with a kMDItemDisplayname that starts with "LibreOffice*"

no surprises then that it doesn't find LO6332.

What has changed here ? The script ? Or the way in which kMDItemDisplayname functions ?

If I rename the LO6332 bundle to LibreOffice6322, the script works...

When did this behaviour get changed ?
Comment 3 Alex Thurgood 2019-11-21 10:00:07 UTC
Possibly , this issue is linked to Apple's new security model, which LO either doesn't support, or doesn't implement.
Comment 4 Xisco Faulí 2019-11-25 15:09:56 UTC
Hello Alex,
Could you please check if this issue is still reproducible in LibreOffice 6.4 beta1 ?
OTOH, i don't think this is a regression, as you mentioned, happening due to the new Catalina's security policy
Comment 5 Alex Thurgood 2019-11-26 07:27:33 UTC
This does indeed appear to be fixed once again in 

Version: 6.4.0.0.beta1
Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920
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


where I can choose which app bundle to install the lang-pack to.

1) Downloaded LO64beta.
2) Installed to Applications folder as LO64b
3) Downloaded FR lang-pack for 64beta
4) Started installation, get offered choice of app bundle location.
5) Select LO64b as destination, installation succeeds.