tor not found

[heinsaris]

Hi,

I installed grin via snap on ubuntu 18.04. I also installed the latest version of tor (0.4.4.6) and it is in my path.

When starting grin.wallet listen, I get an error saying that tor cannot be found:

20210113 20:12:21.123 DEBUG grin_wallet_impls::tor::process - Dropping TOR process
20210113 20:12:21.123 WARN grin_wallet_controller::controller - Unable to start TOR listener; Check that TOR executable is installed and on your path
20210113 20:12:21.123 WARN grin_wallet_controller::controller - Tor Error: Tor Process Error: Process("TOR executable (tor) not found. Please ensure TOR is installed and on the path: Os { code: 2, kind: NotFound, message: "No such file or directory" }")
20210113 20:12:21.123 WARN grin_wallet_controller::controller - Listener will be available via HTTP only

Any idea what is wrong?

Also, how can I tell that the wallet should listen on all interfaces (0.0.0.0) instead of 127.0.0.1? There used to be an entry in grin-wallet.toml (api_listen_interface), but it is no longer present. Perhaps because http is no longer supported?

Thanks for helping out!

[heinsaris]

I have now installed grin-wallet separately and this seems to work as I don't get the tor error.

So it seems that the problem lies within the snap package?

But the separately installed grin-wallet (v5.0.2) cannot connect to my local node?

[quentinlesceller]

Hi @heinsaris do you have tor installed? The new wallet only works throught Tor now.

[heinsaris]

Hi @quentinlesceller. Thanks for replying.

I have installed tor. But for some reason it is not found by grin.wallet installed via snap.

I have installed grin-wallet separately and created a new wallet for it, and I have been able to send grin between the wallet on my mac and the one on Ubuntu.

So the problem lies with the snap package IMHO.

[jaspervdm]

I think this has to do with the fact that packages in snap are confined somehow, they modify the path: https://snapcraft.io/docs/environment-variables

This environment variable is re-written by snapd so that it is consistent with the view of the filesystem presented to snap applications.

Not entirely sure yet what would be the best way for us to fix it.

[bladedoyle]

I noticed this also - snap is in some kind of sandbox/container.
This may help: https://askubuntu.com/questions/1228899/accessing-files-outside-of-home-in-snap-apps

[bladedoyle]

I think the fix is to include the tor executable in the grin snap