# Can't start Slicer on Linux on one machine

**URL:** <https://discourse.slicer.org/t/cant-start-slicer-on-linux-on-one-machine/8175>\
**Category:** Support\
**Created:** [August 26, 2019, 7:12am UTC](https://discourse.slicer.org/t/cant-start-slicer-on-linux-on-one-machine/8175 "2019-08-26T07:12:06Z")\
**Posts on this page:** 1\
**Showing post:** 48

<div class="post-metadata">

**Author:** ![gaoyi.cn](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/gaoyi.cn/32/1422_2.png) [@gaoyi.cn](https://discourse.slicer.org/u/gaoyi.cn)\
**Post date:** [November 2, 2019, 6:56am UTC](https://discourse.slicer.org/t/cant-start-slicer-on-linux-on-one-machine/8175/48 "2019-11-02T06:56:56Z")

</div>

Hi Steve, Hi Andras, @pieper @lassoan

I believed the problem on my machine was that python needs openssl 1.1.0 and up. I then upgraded openssl super build version to 1.1.1d. It then requires curl to be upgraded to 7.66, which I did, and it worked.

I believe this may be related with several recent issues:

- [Building Slicer on a freshly installed Ubuntu 18.04](https://discourse.slicer.org/t/building-slicer-on-a-freshly-installed-ubuntu-18-04/5627/10)  
Initially I though this solves the problem (using both system ssl and curl). But though Slicer built, it doesn’t work properly: numpy can’t be imported.
- [https://issues.slicer.org/view.php?id=4617](https://issues.slicer.org/view.php?id=4617)
- [Slicer crash on fresh build](https://discourse.slicer.org/t/slicer-crash-on-fresh-build/351)  
I had the same problem. I though it was a python problem. But latter found the problem is ssl

Now I have a freshly built Slicer…

---

_[View the full topic](https://discourse.slicer.org/t/cant-start-slicer-on-linux-on-one-machine/8175)._