# Unable to launch alpha on Linux **URL:** \ **Category:** Downloads / Releases\ **Created:** [April 26, 2019, 8:46am UTC](https://discuss.saleae.com/t/unable-to-launch-alpha-on-linux/29 "2019-04-26T08:46:43Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\ **Post date:** [April 26, 2019, 3:47pm UTC](https://discuss.saleae.com/t/unable-to-launch-alpha-on-linux/29/2 "2019-04-26T15:47:35Z")
Sorry for the trouble! After we discovered problems with QT’s QWebEngine, we hastily added code to just launch chrome as an interim solution until we finish integrating Electron ([electronjs.io](http://electronjs.io)). Specifically, on Linux, we: 1. execute `which google-chrome`. If the response is empty, we display the above message. 2. launch the process `google-chrome` with a series of arguments, including `--app` and `--user-data-dir=`, and a few others. Since we’re switching to Electron, it’s unlikely that we’ll change this behavior before removing it entirely. In the meantime, I suspect that a quick symbolic link from google-chrome to chromium might get past this problem, but I haven’t tested it. The front end won’t work with Firefox or other browsers though, which is why we dropped the original fallback that would use Qt’s solution to open the default browser if google-chrome was not found. Let me know if that works, or if you run into trouble with it! - Mark, software lead & co-founder --- _[View the full topic](https://discuss.saleae.com/t/unable-to-launch-alpha-on-linux/29)._