Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to launch the app on macOS Big Sur (kLSNoLaunchPermissionErr) #1129

Closed
DominikPalo opened this issue Nov 14, 2020 · 4 comments
Closed

Comments

@DominikPalo
Copy link

DominikPalo commented Nov 14, 2020

I'm trying to start the precompiled app Printrun-2.0.0rc7-macos on my macOS Big Sur, but it always fails with a "User doesn't have permission to launch the app (managed networks)" error. I tried to use chmod to make the app executable (chmod +x pronterface.app), but it didn't help. Here is my output from the console:

dominik@MBP-Dominik /Applications % sudo open -a pronterface.app
The application /Applications/pronterface.app cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10826 "kLSNoLaunchPermissionErr: User doesn't have permission to launch the app (managed networks)" UserInfo={_LSFunction=_LSLaunchWithRunningboard, _LSLine=2508, NSUnderlyingError=0x7fe1b7c1d0e0 {Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x7fe1b7c0a6b0 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 111}}}}}
@volconst
Copy link
Collaborator

See #1069 (comment)
$ chmod +x /Applications/pronterface.app/Contents/MacOS/pronterface

@DominikPalo
Copy link
Author

@volconst thank you, it helped! I didn't realize that chmod has to be applied to a file inside the .app, not the .app file itself. Everything is ok now :)

@rockstorm101
Copy link
Collaborator

@kliment, @volconst I've seen several issues revolving around the same topic already (executable permission). Is there something we can do about that on the released .zip file itself? Otherwise, we'd better include a note about that on the README.

@volconst
Copy link
Collaborator

If zip files include permissions, then the build procedure should run the chmod before the zip creation.
If not, maybe tar files include permissions, then distribute mac version as tar.
I do not understand the build process, do not have mac, can't fix it myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants