-
Notifications
You must be signed in to change notification settings - Fork 42
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] Slicer does not start after installing SlicerJupyter #77
Comments
Also experiencing this. Have a Apple M3 chip macbook pro. Uninstalled and reinstalled slicer with the same error. |
I have the same problem on my M2 Macbook Air |
@lassoan I compiled locally, packaged and installed via ExtensionManager. When starting Slicer, getting the following:
|
Compiling with ZeroMQ v4.3.4 failed with:
I updated to v.4.3.5 and it compiled. |
When running |
@che85 Thanks for the information, I've updated the build scripts to use ZeroMQ 4.3.5 - 724809a
Thanks for the information, this is good to know.
Does this still occur with the latest Slicer Preview Release? |
@lassoan I just checked with the most recent preview and it is still crashing. |
@jcfr I compiled Slicer on macOS Sonoma 14.4.1 with Apple M2 Max
Compilation failed with the current LibArchive version, so I updated it to use v3.7.4 and everything compiled successfully. After compiling and packaging SlicerJupyter, and installing it through the ExtensionManager, Slicer starts fine, but SlicerJupyter is not loaded. Upon checking I noticed the following error message:
@jcfr Would you happen to know what could be the issue? Thank you. |
I am also experiencing this issue with MacOS for the current Slicer release so I reverted to Slicer 5.2.2 for now where SlicerJupyter extension loads without issue. |
After installing SlicerJupyter from the ExtensionManager and restarting Slicer, Slicer crashes at bootup time. (@lassoan, @jcfr). See the problem report below.
When manually removing SlicerJupyter from the Extensions directory, Slicer starts and doesn't crash.
Problem Report
The text was updated successfully, but these errors were encountered: