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

macos: boot error 'Failed to init from config' ... 'PYTHONHOME is set to ... Setting this environment variable might cause Python to fail.' #359

Open
2 tasks done
budiz1 opened this issue Aug 19, 2024 · 11 comments

Comments

@budiz1
Copy link

budiz1 commented Aug 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Problem description

When i start the latest Freecad weekly build, i get an error that says (in the picture below).

I dont know if that is my computers problem or freecads as this error never showed up before.

Screenshot 2024-08-19 at 11 27 18

Thank you for your feedback,
Budiz

Full version info

I cant enter Freecad

Subproject(s) affected?

None

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@luzpaz
Copy link
Collaborator

luzpaz commented Aug 19, 2024

@JohnOCFII any idea how to solve this ?

@luzpaz luzpaz changed the title I got startup error macos: boot error 'Failed to init from config' ... 'PYTHONHOME is set to ... Setting this environment variable might cause Python to fail.' Aug 19, 2024
@JohnOCFII
Copy link

@JohnOCFII any idea how to solve this ?

Sadly, no. I just downloaded the latest build (38467) for macOS arm -- and it comes across as damaged. I know that there were efforts over the weekend to change the way the bundle was created. Wonder if it is related to that change? See #290
Screenshot 2024-08-19 at 8 52 00 AM

@oursland
Copy link
Collaborator

oursland commented Aug 19, 2024

@JohnOCFII Yes, this is likely due to #290.

@Syres916
Copy link
Contributor

@oursland I think you meant to link #290 rather than a FreeCAD PR from September 2016!!

@oursland
Copy link
Collaborator

@adrianinsaval When I try to debug the application it dies due to signal 9 (SIGKILL), which indicates an external process is terminating the execution.

image

Is this perhaps a signing issue?

@oursland
Copy link
Collaborator

@Syres916 Yes, GitHub automatically linked my text and did so incorrectly.

@oursland
Copy link
Collaborator

I do believe it has to do with code signing or is somehow related. I cannot manually launch the freecad binary. When I move the file outside the FreeCAD.app directory, they begin to execute normally.

I did test this change extensively on my laptop for both #290 and #289, but I will admit I am less knowledgeable about macOS's requirements for running code outside the developer's machine and the related code-signing issues.

Copy link

github-actions bot commented Dec 3, 2024

Hi! This issue hasn’t seen activity in a while. If it’s still relevant, please update to the latest FreeCAD weekly build download here to see if the problem is resolved.

If the issue persists, let us know by adding a comment with any updates or details. Otherwise, we’ll close this issue automatically in 20 days to keep our backlog tidy. Feel free to comment anytime to keep it open. Closed issues can always be reopened.
Thanks for helping improve FreeCAD!

Access additional FreeCAD resources:

@luzpaz luzpaz transferred this issue from FreeCAD/FreeCAD Dec 23, 2024
@luzpaz
Copy link
Collaborator

luzpaz commented Dec 23, 2024

Moved to FreeCAD-Bundle

@adrianinsaval
Copy link
Member

Is this still relevant?

@adrianinsaval
Copy link
Member

Moved to FreeCAD-Bundle

If we don't have confirmation that a stale issue is still relevant please don't bump it, otherwise the stale bot can't do it's job. Not to mention that it's not enabled in the FreeCAD-Bundle repo

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

No branches or pull requests

6 participants