-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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.
'
#15964
Comments
@JohnOCFII any idea how to solve this ? |
Failed to init from config
' ... 'PYTHONHOME is set to ... Setting this environment variable might cause Python to fail.
'
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 FreeCAD/FreeCAD-Bundle#290 |
@JohnOCFII Yes, this is likely due to FreeCAD/FreeCAD-Bundle#290. |
@oursland I think you meant to link FreeCAD/FreeCAD-Bundle#290 rather than a FreeCAD PR from September 2016!! |
@adrianinsaval When I try to debug the application it dies due to signal 9 (SIGKILL), which indicates an external process is terminating the execution. Is this perhaps a signing issue? |
@Syres916 Yes, GitHub automatically linked my text and did so incorrectly. |
I do believe it has to do with code signing or is somehow related. I cannot manually launch the I did test this change extensively on my laptop for both FreeCAD/FreeCAD-Bundle#290 and FreeCAD/FreeCAD-Bundle#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. |
Is there an existing issue for this?
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.
Thank you for your feedback,
Budiz
Full version info
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: