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

Not able to load slic3r on Macos, latest m1. MacOs not able to confirm not malicious #5103

Open
clexp opened this issue Sep 5, 2021 · 5 comments

Comments

@clexp
Copy link

clexp commented Sep 5, 2021

Do not report Prusa3D Slic3r bugs here without confirming it is a problem on a development release of Slic3r, or your issue will be closed. Development builds of Slic3r. Prusa3D Issue Tracker

Describe the bug
"“Slic3r.app” can’t be opened because Apple cannot check it for malicious software."

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Downloads, find .dmg,'
  2. Run the .dmg.
  3. Error ""Slic3r.app” can’t be opened because Apple cannot check it for malicious software."
  4. Error continues: "This software needs to be updated. Contact the developer for more information. This item is on the disk image “Slic3r-master-latest.dmg”. Safari downloaded this disk image today at 17:19 from dl.slic3r.org."
  5. Repeat for all .dmgs in the repo

3D Model and Slic3r Configuration Export
Not applicable

Expected behavior
To open normally

Screenshots
Nothing more to show besides error above

Desktop (please complete the following information):
M1 MacBook Pro, 2021, BigSur 11.5.1

Additional context
Sorry if I am missing something dumb.

@billdwhite
Copy link

If you go into the security&privacy control panel, you can tell the OS to bypass that warning and open the file

@clexp
Copy link
Author

clexp commented Nov 5, 2021

Ah that's great, That ties in with some other issues I had, all working now, thanks so much.
regards

@lordofhyphens
Copy link
Member

lordofhyphens commented Nov 7, 2021 via email

@billdwhite
Copy link

@lordofhyphens: I don't think there is much to debug. The program will still run, but you have to just get past the restriction warning; the true fix would be to get the application properly certified/trusted to run a mac which would bypass that warning but it is still usable at the moment (although it does not run on Mac OS Montery; I get a "perl-local quit unexpectedly" since that update and the program dies immediately and is unusable, but that's belongs in a new issue)

@lordofhyphens
Copy link
Member

lordofhyphens commented Nov 8, 2021 via email

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