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
[Bug] MacOS crash at startup all the time (critical) #166
Comments
Working fine here, same version of Freecad running on Intel MacOS 12.6 It seems to be a problem with your QT library, check if you have it installed somewhere in your system and is loading from there instead of the embedded library (LD_LIBRARY_PATH?) |
Also have this issue:
OS Info
Tried
debug log ..
|
This bug is related to compile parameters on qtwebengine it seems; Freecad is using
|
Tested the lateste weekly-bundle and it has the same issue
|
digging a little deeper
The file that attempts to load the ICU file is Chromium - presumably qtwebengine is loading it I have tried locating the file |
I can confirm that symlinking the icudtl.dat and *.pak files into /Applications/FreeCAD.app/Contents/Resources/ will make it work. |
This works for me:
|
CC @ipatch |
Closed dupe FreeCAD/FreeCAD#7787 in favor of this ticket. Can we get some traction on this ? |
Thanks this worked for me too. |
Hi @looooo, can we tweak the conda macos build with this symlink fix ? |
I hope this does the job: |
Thank! |
Should it be included into a development version yet? Just tried FreeCAD_weekly-builds-31432-2022-12-25-conda-macOS-x86_64-py310.dmg (5ca6d46ff76965ddb4ecabfe1d71cc708a64cac72e80612e79e1772119acfb21) with no luck:
Filesystem formatted APFS case sensitive. Symlinking Resources -> resources makes it work. |
Installing version from: https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds, there is for MacOS - ARM version from 2022-12-31 and still is not fixed there, but fix with symlink helped me. I tried only rename On my MAC I always use use case-sensitive file system, so please do not forget on us |
This information made me happy. Making a symbolic link worked well. |
Could someone correct this bug on the stable and official version? so sad it takes years for a cast issue to be corrected.... so bad that a so small correction takes so much time ! I also rename the folder resources into Resources and it works well, should be a 5 minutes correction .... if no one cares about it, how can I push this modification for next stable release? |
@chennes is this something you can correct in the macOS conda build ? |
Moved to FreeCAD-Bundle |
looo mentioned 2a602fb as potential fix, but I see it was only applied to osx-arm script, maybe it should be applied to the regular osx bundle script too? I suggest one of the interested parties to make a PR doing this. |
If my quick scan of this topic is correct, then 7dc3210 will fix this |
It would be nice to trigger a new appimage build to see if this fixes the issue (instead of waiting a week for new builds to occur) |
When a commit is made to this repo a new bundle is made automatically, a fixed bundle should be available in ~30min |
the new bundle is available, please test and report.
|
@krl91 👆 |
Hi,
ls /Applications/FreeCAD.app/Contents/Resources/ also the solution on 7dc3210 is a quick and dirty one: why creating a link for a folder that has the wrong name... |
870a89b should have fixed this, I'm going to assum it did. Please comment or reopen if this issue is still present on the latest release |
Is there an existing issue for this?
Forums discussion
https://forum.freecadweb.org/viewtopic.php?f=3&t=71835&p=626089#p626089
Version
0.20 (Release)
Full version info
Subproject(s) affected?
No response
Issue description
I'm using MacOS 12.5.1 (MacIntel) and just installed last Downloadable version of FreeCAD for MacOS (20.1)
When I launch it I have the small window that is showing the loading of FreeCAD and the it crah all the time itself, so it sound to be a critical bug.... so I go back on FreeCAD 19 that works well..
Same issue on FreeCAD 0.21.
FreeCAD 0.19 works
Anything else?
Code of Conduct
The text was updated successfully, but these errors were encountered: