Details
Description
When you drag the Application in the DMG to the Applications folder on your computer the Application owner is set as the current user.
This should not be the case as it prevents the application launching correctly when using the computer with another user account.
If the application is installed by an administrator or system user then when the application is run by an actual user the application fails to launch unless launched from the terminal. instead hanging as if the application was launched with
/Applications/Jalview.app/Contents/MacOS/JavaApplicationStub
rather then
/Applications/Jalview.app/Contents/MacOS/jalview
This is partially apparent if your organisation uses a distribution method such as Munki or Jamf to install and update applications on users computers.
This should not be the case as it prevents the application launching correctly when using the computer with another user account.
If the application is installed by an administrator or system user then when the application is run by an actual user the application fails to launch unless launched from the terminal. instead hanging as if the application was launched with
/Applications/Jalview.app/Contents/MacOS/JavaApplicationStub
rather then
/Applications/Jalview.app/Contents/MacOS/jalview
This is partially apparent if your organisation uses a distribution method such as Munki or Jamf to install and update applications on users computers.
Attachments
Issue Links
- depends on
-
JAL-3620 autoupdater-blocked when jalview is run as user
- Closed
-
JAL-3631 Allow jalview auto-updates to download to and work from separate user-space directory
- Closed
-
JAL-4013 Add a facility in Jalview application for user to put jalview launch script in their PATH
- Open
-
JAL-4057 Update installer and instructions to support installation in multi-user context
- Ready for testing