Linux packaged browser failing to launch.
See original GitHub issueSteps to reproduce:
- Clone Safe_browser repo after PR #637
- Follow steps https://github.com/maidsafe/safe_browser#compiling to package the browser locally.
- Navigate to the release folder and try to launch browser with
./safe-browser
Expected result:
Browser will launch OK
Actual result:
Browser fails to launch, error message is returned: Segmentation fault (core dumped)
Environments:
This has been replicated in Ubuntu 18.04 VM and Linux Mint 19 Cinnamon native machine.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Issues - GitHub
launch : Failed to launch chromium because executable doesn't exist at /home/jenkins/.cache/ms-playwright/chromium-844399/chrome-linux/chrome #5767.
Read more >Error: Failed to launch the browser process puppeteer
What works for me was to download chromium manually sudo apt-get install chromium-browser . And then, tell Puppeteer where chromium is located :...
Read more >Unable to Launch Tor Browser [duplicate] - Ask Ubuntu
Try to install this package with this command: sudo apt install libcanberra-gtk-module libcanberra-gtk3-module.
Read more >Troubleshooting — Anaconda documentation
To resume the download using Chrono Download, from your top browser menu, click on the Chrome menu button, then click “Downloads.” Select the...
Read more >Troubleshooting Windows Subsystem for Linux | Microsoft Learn
Open Control Panel -> Programs and Features -> Turn Windows Feature on or off -> Check Windows Subsystem for Linux or using the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@calumcraig [UPDATE]: Scratch that. I’m able to reproduce.
Can confirm that the roll back of PR #637, PR #641 has resolved this issue. SAFE Browser launches as expected on Linux Mint 19.
Tested on Ubuntu 18.04 and behaviour has returned to the previous - #627 is still seen. Workaround (as described in browser README) resolves the issue:
sudo apt-get install libgconf-2-4
.