Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.
Sign up to join this community
I'm trying to install OS X Yosemite through 'Install OS X Yosemite.app' downloaded from the Internet. When I try to open it by double clicking it, nothing happens. When I use the terminal I get the following message:
$ open /Applications/Install\ OS\ X\ Yosemite.app/
LSOpenURLsWithRole() failed with error -10810 for the file /Applications/Install OS X Yosemite.app.
That would seem to imply the executable within the package isn't actually executable.
Where did you get it from?
If not Apple, I'd leave it well alone. If it was from Apple, try this in Terminal
chmod +x /Applications/Install\ OS\ X\ Yosemite.app/Contents/MacOS/InstallAssistant
Contents/MacOS/JavaApplicationStub in my .app directory.
Aug 26, 2015 at 18:46
I had this error with Pentaho 8. This command solved it for me:
xattr -dr com.apple.quarantine '/Applications/Pentaho/design-tools/data-integration/Data Integration.app'
OSX will "quarantine" files that are downloaded from untrusted sources.
You can see if this is your problem by listing the xattrs.
cd /path/to/your/ApplicationName.app
xattr -l Contents/MacOS/*
If you see "com.apple.quarantine" then that's your problem.
I mysteriously got this on Yosemite for the Calendar app. Launching the actual binary worked for me.
bash$ /Applications/Calendar.app/Contents/MacOS/Calendar &
There did not seem to be a permissions issue that could be fixed with chmod.
The symptom I got originally was "The application "Calendar.app" is not open anymore" when attempting to click calendar reservations in Mail.app.
xattr but it's still misbehaving (now worse than when I posted this answer).
I had this error when attempting to run an application from an ssh terminal while the screen was locked. The app complained that the user did not have permission to open a GCWindow.
Unlock the screen by logging in, and my app now launches fine.
As commented by @Matt Vukas in the currently accepted answer, it appears that a good thing to check might be simply changing the permissions of the file that gets executed within the .app directory.
# Note: change YourApp to the app name (in both places!)
chmod +x path/to/YourApp.app/Contents/MacOS/YourApp
This command worked for me with a MacOS build that was exported from Unity (the game development engine).
I got the same error when trying to run an app on my system. Following the @tripleee answer (trying to launch the app's binary) gave me a more instructive message:
wsee$ cd /Applications/someapp/Contents/MacOS
wsee$ ./someapp
2022-02-16 11:34:06.010 someapp The application with bundle ID XYZ is running setugid() which is not allowed. Exiting.
Sure enough, when I checked the setuid bit was set (bolded in example below):
wsee$ ls -l
drw**s**r-xr-x@ 3 wsee staff 96 12 Jul 2021 someapp
When an executable has its setuid bit set then it will be run as the file owner no matter which user launches it. In the above example, if user Bob launches someapp then it will run with the effective user id of 'wsee' even though it is Bob running the app.
Setuid (aka set-user-ID-on-execution and SUID) presents a serious security risk when used on executables owned by root, because if a vulnerability exists in the executable then an attacker might be able to execute code as root, giving them limitless control over the system.
Removing the setuid bit was a simple matter of running:
chmod u-s someapp
What helped me with this error message under macOS Mojave 10.14.6 was to move the .app file from the Downloads directory to the /Applications directory.
Then I could start the .app file without problems.
