# 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:** 38

<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:** [October 31, 2019, 4:00am UTC](https://discourse.slicer.org/t/cant-start-slicer-on-linux-on-one-machine/8175/38 "2019-10-31T04:00:51Z")

</div>

Solved using ssl:

> [@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):
>
> Here is what I am getting when I execute gdb with bin/SlicerApp-real: (gdb) exec-file SlicerApp-real (gdb) run Starting program: /home/satya/wrk/Slicer/build/Slicer-build/bin/SlicerApp-real [Thread debugging using libthread\_db enabled] Using host libthread\_db library “/lib/x86\_64-linux-gnu/libthread\_db.so.1”. [New Thread 0x7fffad95a700 (LWP 8620)] qt5ct: using qt5ct plugin [New Thread 0x7fffa59e1700 (LWP 8621)] [New Thread 0x7fffa5127700 (LWP 8622)] Thread 1 “SlicerApp-real” received s…

---

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