Earlier quoted context omitted.
Thank you for pointing this out. I've addressed the issue, and it should now be fixed in version 0.2.1, which is available for download on the website. Please update to the latest version, and let me know if you encounter any more problems.
This problem persist on version 0.2.3
On Linux, the application currently uses the command:
```bash
google-chrome --proxy-server= --ignore-certificate-errors-spki-list=
```
to launch Chrome.
For some users, this command doesn't seem to work properly. I'm working on adding a feature that will allow you to manually set the command used to launch Chrome if the default one isn't working on your system.
In the meantime, you can manually launch Chrome with the arguments shown above. Just replace `` and `` with the appropriate values for your setup.