For some time I've been using Tor (in conjunction with Vidalia) with Windows, and i've been trying to get it working on Linux.
Since there is no Vidalia package available in the Ubuntu repository, I downloaded Vidalia's source code and built it without problems.
I got the latest Tor package from noreply.org: (It's for breezy but should work fine on edgy, right?)
When I try to launch tor from vidalia, I get the following error:
The log says:
I then killed the Tor process and tried again.
Vidalia gave me a new error when I tried to launch tor through it, that it could not connect to /var/log/tor/log. I changed the permissions and tried again.
This time, Tor was able to start but there was a new Vidalia error:
"control Socket is not connected"
The message log said:
If I try to activate Vidalia again, it will crash.
How can I get this working?
Since there is no Vidalia package available in the Ubuntu repository, I downloaded Vidalia's source code and built it without problems.
I got the latest Tor package from noreply.org: (It's for breezy but should work fine on edgy, right?)
Code:
deb http://mirror.noreply.org/pub/tor breezy main deb-src http://mirror.noreply.org/pub/tor breezy main
When I try to launch tor from vidalia, I get the following error:
Code:
Vidalia detected that Tor exited unexpectedly. Please check the message log for indicators about what happened to Tor before it exited.
The log says:
Code:
Feb 11 16:44:52:122 [Notice] Tor v0.1.1.26. This is experimental software. Do not rely on it for strong anonymity. Feb 11 16:44:52:124 [Notice] Initialized libevent version 1.1a using method epoll. Good. Feb 11 16:44:52:125 [Notice] connection_create_listener(): Opening Socks listener on 127.0.0.1:9050 Feb 11 16:44:52:126 [Warning] connection_create_listener(): Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running? Feb 11 16:44:52:127 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports. Feb 11 16:44:52:128 [Error] tor_init(): Reading config failed--see warnings above. For usage, try -h.
I then killed the Tor process and tried again.
Vidalia gave me a new error when I tried to launch tor through it, that it could not connect to /var/log/tor/log. I changed the permissions and tried again.
This time, Tor was able to start but there was a new Vidalia error:
"control Socket is not connected"
The message log said:
Code:
Feb 11 17:00:07:534 [Notice] Tor v0.1.1.26. This is experimental software. Do not rely on it for strong anonymity. Feb 11 17:00:07:538 [Notice] Initialized libevent version 1.1a using method epoll. Good. Feb 11 17:00:07:538 [Notice] connection_create_listener(): Opening Socks listener on 127.0.0.1:9050 Feb 11 17:00:07:539 [Notice] connection_create_listener(): Opening Control listener on 127.0.0.1:9051
If I try to activate Vidalia again, it will crash.
How can I get this working?