# \[solved\] 0.4.9.9.3 amd64 not starting on Debian 9.0 "Stretch"

**URL:** <https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302>\
**Category:** Support\
**Created:** [June 20, 2017, 6:40pm UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302 "2017-06-20T18:40:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon10998290](https://bisq.community/letter_avatar/anon10998290/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon10998290](https://bisq.community/u/anon10998290)\
**Post date:** [June 20, 2017, 6:40pm UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302/1 "2017-06-20T18:40:23Z")

</div>

New Debian stable “Stretch” was released some days ago.

I dist-upgraded from Jessie to Stretch, and now Bitsquare 0.4.9.9.3 does not run anymore.

Error message is ‘Segmentation fault’.

```auto
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.0 (stretch)
Release: 9.0
Codename: stretch
$ uname -a
Linux bitcoind 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux

$ /opt/Bitsquare/Bitsquare 
Segmentation fault

```

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 20, 2017, 9:15pm UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302/2 "2017-06-20T21:15:57Z")

</div>

Hm… no idea. maybe try to reinstall it.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 24, 2017, 1:48pm UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302/6 "2017-06-24T13:48:42Z")

</div>

I will add that JVMUserOptions to the next release which will get out soon.

---

<div class="post-metadata">

**Author:** ![jkepler](https://bisq.community/user_avatar/bisq.community/jkepler/32/2601_2.png) [@jkepler](https://bisq.community/u/jkepler)\
**Post date:** [June 29, 2017, 9:37am UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302/7 "2017-06-29T09:37:31Z")

</div>

I had the same problem with bisq not starting after upgrading to Debian 9.0 Stretch. I’d copied my data directory to my old netbook (which I hadn’t upgraded from Debian Jessie) and bisq worked fine (except for being painfully slow, but that’s due to the dinky Atom processor and only 1 GB of non-upgradable RAM soddered to the motherrboard on that little Nokia Booklet 3G), so I was able to finish my active trade.

I tried @anon10998290’s solution, and it works perfectly for me. So I agree that including that fix in the next bisq upgrade would help folks using Debian Stretch and its derivatives like Ubuntu and Linux Mint.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 29, 2017, 3:00pm UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302/8 "2017-06-29T15:00:14Z")

</div>

The new release has that VM option ans hopefully that Kernel issue is solved by that.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [July 3, 2017, 7:34pm UTC](https://bisq.community/t/solved-0-4-9-9-3-amd64-not-starting-on-debian-9-0-stretch/2302/10 "2017-07-03T19:34:41Z")

</div>

Ah good then the jre option is sufficient.