I’m trying to run Slicer 5.8.1 on CentOS 7.9 server with 3 extensions: SlicerDMRI, SlicerWMA, UKFTractography. Everything works fine with DMRI and UKFT, but every time I try to install SlicerWMA the program doesn’t reopen after I click on the restart button. Any subsequent attempt to launch Slicer again result in the splash screen followed by this error:
$ ./Slicer
error: [/apps/lib/3dslicer/5.8.1/bin/SlicerApp-real] exit abnormally - Report the problem.
I tried ./Slicer --disable-settings and ./Slicer --disable-modules with the same result.
Anyone know how to further troubleshoot this issue? Thank you!
We checked today’s Slicer Preview build (5.9.0) on linux and the SlicerWMA extension no longer prevents Slicer from starting up and SlicerDMRI and UKFTractography work as expected.
For the current release, SlicerWMA is still the older version that prevents Slicer from starting, so if you need to use 5.8.1 don’t install SlicerWMA.
It turns out SlicerWMA is actually just a stub for a module in development that didn’t add the expected functionality, so if you want to try tract parcellation you can use the whitematteranalysis python approach directly and the results should still be compatible with SlicerDMRI.
@pieper I see that you have removed the SlicerWMA extension from being available for the Slicer Preview release with the below commit. Is that intended? Is that how you intend to fix the slicer startup issue by removing the extension from the index?
@jamesobutler the underlying problem was actually fixed in whitematteranalysis but then we realized that the SlicerWMA module didn’t do anything particularly useful (it was an unfinished stub from an earlier developer) so we didn’t want to leave a boobytrap that installed the wrong VTK.
I made PRs to remove WMA from Neuro.
We were planning to ask to have the existing extension removed from the 5.8.1 release extensions so that people would not get bit by this. @jcfr or @Sam_Horvath do you have access to remove SlicerWMA builds from the release server?
This whole exercise makes me look forward to getting this functionality in place.