Vidalia 0.3.0: "Start Tor" button without effect
As already reported on or-talk, I'm unable to get Vidalia 0.3.0 to connect to the ControlPort of an already running Tor process.
With Vidalia 0.2.12 it works:
fk@r500 ~ $/usr/obj/usr/ports/net-mgmt/vidalia/work/vidalia-0.2.12/src/vidalia/vidalia --loglevel debug May 13 14:23:04.497 [notice] Resetting UI translation to English default. May 13 14:23:04.498 [info] Removing all currently installed UI translator objects. May 13 14:23:04.647 [notice] Vidalia 0.2.12 using Qt 4.7.2 May 13 14:23:04.724 [notice] QtWarningMsg: Application asked to unregister timer 0x9000004 which is not registered in this thread. Fix application. May 13 14:23:04.839 [info] Using Tor's GeoIP database for country-level relay mapping. May 13 14:23:05.008 [notice] Tor status changed from 'Unset' to 'Stopped'. May 13 14:23:06.980 [notice] Tor status changed from 'Stopped' to 'Starting'. May 13 14:23:07.020 [notice] Tor status changed from 'Starting' to 'Started'. May 13 14:23:07.022 [debug] QtDebugMsg: torcontrol: Control connection status changed from 'Unset' to 'Connecting' May 13 14:23:07.023 [debug] QtDebugMsg: torcontrol: Connecting to Tor (Attempt 1 of 5) May 13 14:23:07.025 [debug] QtDebugMsg: torcontrol: Starting control connection event loop. May 13 14:23:07.026 [debug] QtDebugMsg: torcontrol: Control connection status changed from 'Connecting' to 'Connected' May 13 14:23:07.030 [notice] Tor status changed from 'Started' to 'Authenticating'. May 13 14:23:07.035 [debug] QtDebugMsg: torcontrol: Control Command: PROTOCOLINFO 1 May 13 14:23:07.037 [debug] QtDebugMsg: torcontrol: Control Reply: 250 PROTOCOLINFO 1 250 AUTH METHODS=NULL 250 VERSION Tor="0.2.3.1-alpha" 250 OK [...]
With 0.3.0 it 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. Tor is running jailed Vidalia isn't. I don't think it matters here, though.
I'm not using a "SystemTray" application which Vidalia used to require several years ago (otherwise one wouldn't be able to start a Window), but not lately.
Given the "QtWarningMsg: QSystemTrayIcon::setVisible" message that's only in the 0.3.0 output I'm mentioning it anyway. I'll try to see if installing a "SystemTray" application makes a difference.