-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Pretty Minor] Issue with electron apps when running with proxychains4 #586
Comments
I don't think it really has much to do with proxychains however I thought I would mention it just in case including anyone who may encounter this in the future. |
that's a known issue - search for sandbox in the issues. though it's nice that you document a workaround, which may be useful for some. |
Interesting. Kind of a flaw but is nothing really. The work around doesn't always work for some apps like I said which means you would need to find an additional work around if you cannot use flatpak to install the same application. |
Up to you but you could add this issue to the read me or I can make a pull request to add it. |
Config and other information has not changed since my last issue post which is here: #585
I will add new config and other edits if needed in the future.
Not sure if it is either electrum or proxychains related issue. When running an app that uses electrum like discord, signal etc you will be required to add
--no-sandbox --in-process-gpu
at the end of the target if you want to route its traffic through proxychains and have it boot successfully.If you do not parse the workaround above then the process will just throw an error and exit which is supplied at the bottom and in the screenshot below
Although this work around does not always work with some applications like discord as I had to flatpak install it for it to work compared to the debian install.
I will provide a screenshot below to help show the issue:
The second time I had run signal with proxychains and also parsing the workaround mentioned above is a successful start and run. The above is pretty obvious.
Console output in event of error:
The text was updated successfully, but these errors were encountered: