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.' #15964

Open
2 tasks done
budiz1 opened this issue Aug 19, 2024 · 7 comments
Labels
OS: macOS Packaging/building Related to building, compiling or packaging FreeCAD Packaging: Conda Conda packaging related Type: Known issue

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
@budiz1 budiz1 added the Status: Needs triage Missing triage label Aug 19, 2024
@luzpaz luzpaz added Packaging/building Related to building, compiling or packaging FreeCAD OS: macOS Packaging: Conda Conda packaging related and removed Status: Needs triage Missing triage labels Aug 19, 2024
@luzpaz
Copy link
Contributor

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
Sponsor

@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 FreeCAD/FreeCAD-Bundle#290
Screenshot 2024-08-19 at 8 52 00 AM

@oursland
Copy link
Contributor

oursland commented Aug 19, 2024

@JohnOCFII Yes, this is likely due to FreeCAD/FreeCAD-Bundle#290.

@Syres916
Copy link
Contributor

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

@oursland
Copy link
Contributor

@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
Contributor

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

@oursland
Copy link
Contributor

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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS: macOS Packaging/building Related to building, compiling or packaging FreeCAD Packaging: Conda Conda packaging related Type: Known issue
Projects
None yet
Development

No branches or pull requests

5 participants