Tomas Touceda <chiiph@xxxxxxxxxx> wrote: > Vidalia-0.3.0-alpha is out! > We are going to be doing a series of alpha releases in parallel with the > stable 0.2.x to have a wider audience for some changes that are kind of > "core" for Vidalia, or they are really big to put them on the stable > before testing them for a while. > > We need more eyes, but I want to be clear about the "alpha" part in the > version. The bundles that were just announced they also have an alpha > version of Tor, the latest libevent, the latest openssl, and so on, not > just this Vidalia release. So be aware of this while running them. My Vidalia use case is to manually let it connect to the control port of an already running Tor process. With 0.2.12 this works and looks like this: fk@r500 ~ $/usr/obj/usr/ports/net-mgmt/vidalia/work/vidalia-0.2.12/src/vidalia/vidalia --loglevel notice May 13 12:48:02.325 [notice] Resetting UI translation to English default. May 13 12:48:02.427 [notice] Vidalia 0.2.12 using Qt 4.7.2 May 13 12:48:02.520 [notice] QtWarningMsg: Application asked to unregister timer 0x9000004 which is not registered in this thread. Fix application. May 13 12:48:02.777 [notice] Tor status changed from 'Unset' to 'Stopped'. May 13 12:48:05.109 [notice] Tor status changed from 'Stopped' to 'Starting'. May 13 12:48:05.140 [notice] Tor status changed from 'Starting' to 'Started'. May 13 12:48:05.153 [notice] Tor status changed from 'Started' to 'Authenticating'. May 13 12:48:05.159 [notice] Authenticating using 'null' authentication. May 13 12:48:15.663 [notice] Tor status changed from 'Authenticating' to 'Authenticated'. May 13 12:48:15.664 [notice] Tor status changed from 'Authenticated' to 'Circuit Established'. May 13 12:49:46.896 [notice] Cleaning up before exiting. May 13 12:49:46.905 [notice] Vidalia is exiting cleanly (return code 0). [...] With 0.3.0 this doesn't work. Vidalia starts with the progress bar already at 18% even though it's not supposed to connect automatically and the "Start Tor" button doesn't seem to do anything: fk@r500 ~ $/usr/obj/usr/ports/net-mgmt/vidalia-devel/work/vidalia-0.3.0/src/vidalia/vidalia --loglevel debug May 13 12:54:21.401 [notice] Resetting UI translation to English default. May 13 12:54:21.402 [info] Removing all currently installed UI translator objects. May 13 12:54:21.517 [notice] Vidalia 0.3.0 using Qt 4.7.2 May 13 12:54:21.670 [info] Using Tor's GeoIP database for country-level relay mapping. May 13 12:54:21.698 [notice] QtWarningMsg: QSystemTrayIcon::setVisible: No Icon set May 13 12:54:21.704 [notice] QtWarningMsg: Application asked to unregister timer 0x3600000b which is not registered in this thread. Fix application. ^CMay 13 12:55:30.490 [notice] Cleaning up before exiting. May 13 12:55:30.496 [notice] Vidalia is exiting cleanly (return code 0). The behaviour seems to be the same when trying to use a Control Socket instead of a Control Port. I'm using FreeBSD 9.0-CURRENT amd64. Is manually connecting to an already running Tor process working for anyone else? Fabian
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ tor-talk mailing list tor-talk@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk