(it was the only place I found with legacy releases).
And uncompressed the ZIP file to folder of my choice. When trying to start the application, the splash screen is shown for a few seconds, but then the process terminates with the following error:
me@machine:/opt/Slicer-4.10.2-linux-amd64$ ./Slicer
error: [/opt/Slicer-4.10.2-linux-amd64/bin/SlicerApp-real] exit abnormally - Report the problem.
Can I expect an old release to work on a more recent OS version? If yes, Is there, is there a location where Slicer keeps a log of the events or an error trace so that I can share it?
In general yes, old releases should still work, but some sometimes the OS changes. I’ve had very old executables work on windows, so maybe try that instead of linux.
@jhlegarreta, maybe you should try to build Slicer yourself, but be aware that this will probably require some patching. I don’t think it will compile out-of-the-box
If you want to get an idea where the binary failing to start on linux you can start a shell with the environment variables set, something like: ./Slicer --launch xterm
and then in the new window try: sudo strace Slicer
If you look at the end of the output you’ll see what happened before it crashes. If it’s a missing file or similar you may be able to make things work.
Alternatively you might just run an older linux version in a docker container. You could tunnel the X display to show the old slicer on your newer desktop. It’s a bit of an ugly workaround but it might get you past whatever issue you are seeing.
As a general rule we only support the current releases to avoid diverting our efforts too much.
I am attaching two files for the sake of completeness:
First one (could only get a screenshot, sorry) corresponds to the terminal messages I get when running ./Slicer --launch xterm. Of course, on my Ubuntu 22.04 I do not have Python 2.7, but I assume Slicer bundles its own interpreter (even if 2.7 seems old for a 2019 4.2.10 release). Installing 2.7 is not an option if that is the main issue.
Second one (dropbox link; current discourse instance does not allow uploading text files) corresponds to the messages I get when running sudo strace Slicer. Not sure what the BadShmSeg (invalid shared segment parameter) message means, but it does not look straightforward to debug. There are other errors in the trace that seem equally hard to me to guess what they mean/how to fix them. All seem related to X11 windowing system.
Alternatively you might just run an older linux version in a docker container
If this involves building the docker image myself, I do not think this is doable given some constraints I have.
As a general rule we only support the current releases to avoid diverting our efforts too much.
I completely understand, so if things do not seem they can be fixed easily, I would understand not continuing to put time on this on your side.
Using Slicer 4.10.2 was probably just due to the fact that at the time it was the version they had working on their systems, for sure before Ubuntu 22.04 was available, and probably on a different OS (most likely macOS).
It would be great if you can try getting those DTI extensions working with latest Slicer.
I ignore the effort that this requires, and if I need to do this in my spare time, then I simply may not have the bandwidth; I am already a contributor/maintainer on a number of other open-source projects that also require time.
Thanks for the tip JC. Although that indeed fixes the xterm launch error, the second command (sudo strace Slicer) still produces the same error as in the earlier post.
