# Unable to start Slicer 4.10.2 on Ubuntu 22.04

**URL:** <https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225>\
**Category:** Support\
**Created:** [June 26, 2023, 2:14am UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225 "2023-06-26T02:14:56Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 26, 2023, 2:14am UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/1 "2023-06-26T02:14:56Z")

</div>

Hi,  
I have downloaded 3D Slicer 4.10.2 from this data archive:  
[https://slicer-packages.kitware.com/#collection/5f4474d0e1d8c75dfc70547e/folder/5f4474d0e1d8c75dfc705482](https://slicer-packages.kitware.com/#collection/5f4474d0e1d8c75dfc70547e/folder/5f4474d0e1d8c75dfc705482)

(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:

```auto
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?

Thanks.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [June 26, 2023, 1:14pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/2 "2023-06-26T13:14:31Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 26, 2023, 1:54pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/3 "2023-06-26T13:54:09Z")

</div>

Unfortunately, trying this on Windows is really not an option in this case/for me.

---

<div class="post-metadata">

**Author:** ![RafaelPalomar](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rafaelpalomar/32/1436_2.png) [@RafaelPalomar](https://discourse.slicer.org/u/RafaelPalomar)\
**Post date:** [June 26, 2023, 2:48pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/4 "2023-06-26T14:48:14Z")

</div>

@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

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 26, 2023, 2:53pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/5 "2023-06-26T14:53:21Z")

</div>

Sorry Rafael, but I am willing to avoid trying to build it myself, even more so if chances are that I will run into other issues.

But thanks for the suggestion and the support.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [June 26, 2023, 5:06pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/6 "2023-06-26T17:06:49Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 26, 2023, 7:23pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/7 "2023-06-26T19:23:10Z")

</div>

Thanks for the effort Steve.

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.

Thanks.

 ![slicer_xtem_launch](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/7/47ffa8db6f59b53a70e0a413b804b172561254e2.png)

> **[slicer\_xterm\_log.txt](https://www.dropbox.com/s/v5kspchfw8ics58/slicer_xterm_log.txt?dl=0)**
>
> Shared with Dropbox

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [June 26, 2023, 7:34pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/8 "2023-06-26T19:34:02Z")

</div>

I assume using Slicer 4.10.2 is because it had DTI extensions available and latest Slicer does not have this extensions (re [Previously available extensions no longer available on 5.2.2 - #2 by jamesobutler](https://discourse.slicer.org/t/previously-available-extensions-no-longer-available-on-5-2-2/30226/2)) . It would be great if you can try getting those DTI extensions working with latest Slicer.

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 26, 2023, 7:47pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/9 "2023-06-26T19:47:50Z")

</div>

> I assume using Slicer 4.10.2 is because it had DTI extensions available and latest Slicer does not have this extensions (re [Previously available extensions no longer available on 5.2.2 - #2 by jamesobutler](https://discourse.slicer.org/t/previously-available-extensions-no-longer-available-on-5-2-2/30226/2)) .

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.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [June 26, 2023, 9:40pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/10 "2023-06-26T21:40:01Z")

</div>

To avoid issue related to virtual env wrapper, you may introduce a variable called `VIRTUALENV_DISABLED`.

For example, see

> <https://github.com/jcfr/dotfiles/blob/088697a0a16b0ce4cc785aab0b7f09665d55260d/.exports#L8-L19>

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/8/b/8bad9b7c14aea2bf2ffca96d452a6547aca8aa5d.png)

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 27, 2023, 3:13pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/11 "2023-06-27T15:13:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [June 27, 2023, 10:37pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/12 "2023-06-27T22:37:14Z")

</div>

Sorry, that was a typo on my part. After launch in the new shell try `sudo strace SlicerApp-real`

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 28, 2023, 2:58pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/13 "2023-06-28T14:58:47Z")

</div>

Thanks for the effort Steve.

It looks like Slicer is unable to find some shared libraries/expect them to be somewhere where they are not. Not sure how this can be approached.

 ![slicer_4-10-2_ubuntu_22-04_start_issue_1](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/7/e/7e7e421b27690346f148d2fe0e899aba010595a0.png)  
 ![slicer_4-10-2_ubuntu_22-04_start_issue_2](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/0/8/08034b567c0859a8f539ee5eeefa423d66432040.png)

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [June 28, 2023, 7:58pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/14 "2023-06-28T19:58:15Z")

</div>

Did you do this part:

> [@pieper](#):
>
> `./Slicer --launch xterm`  
> and then in the **new window** try:

(corrected)

```auto
strace SlicerApp-real

```

---

<div class="post-metadata">

**Author:** ![jhlegarreta](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jhlegarreta/32/66542_2.png) [@jhlegarreta](https://discourse.slicer.org/u/jhlegarreta)\
**Post date:** [June 28, 2023, 8:04pm UTC](https://discourse.slicer.org/t/unable-to-start-slicer-4-10-2-on-ubuntu-22-04/30225/15 "2023-06-28T20:04:58Z")

</div>

> Did you do this part:

Sorry Steve, yes.