Opened 5 years ago

Closed 5 years ago

#82 closed defect (fixed)

Vidalia cannot start tor.exe

Reported by: losepete Owned by:
Priority: blocker Component: qtapps
Version: Keywords:


Yes, I set the correct path to tor.exe in the Vidalia settings.

Looking at the message log I see this:-

May 15 02:00:13.441 [Notice] Tor v0.2.4.20 (git-3cb5c70beec5bf46) running on OS/2 with Libevent 2.0.21-stable and OpenSSL 1.0.0g. May 15 02:00:13.441 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at May 15 02:00:13.441 [Warning] Unable to open configuration file "J:/PROGRAMS/TOR/VIDALIA/I:\USERS\PETER\HOME\.vidalia\torrc". May 15 02:00:13.441 [Error] Reading config failed--see warnings above.

Looks like there is a problem with vidalia as it seems to be appending the configuration file drive:\path\filename to the drive:\path that vidalia is installed in and then passing the resulting mess to tor which then bitches that it cannot open(find) the configuration file.

Change History (3)

comment:1 Changed 5 years ago by gianfli

Try use Tor v0.2.4.21 for OS/2 instead of Tor v0.2.4.20 for OS/2 Tor v0.2.4.21 for OS/2 is available here: Check also if you have all the main dynamic libraries (*.dll) described inside both packages and related dependencies, maybe I missed something. Configuring tor is something personal and reflect your desire (client, relay, bridge), a good starting point maybe this: Consider that OS/2 Vidalia version follow the unix statements (ORPort 9050 instead of 443 for relay, C:/usr/local/bin for paths and so on), however all of them are optional, don't worry. Check also if both programs are in your config.sys PATH statement (it whould be better). If at the end all works, please, close this ticket. Regards.

comment:2 Changed 5 years ago by losepete

Having updated Tor to v0.2.4.21 the problem has gone away.

So the problem was not with Vidalia munging the paths but with Tor v0.2.4.20

I'll certainly have a look through the docs to see what I need to add to the configuration.

I guess you can consider this ticket Closed.

comment:3 Changed 5 years ago by gianfli

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.