Vidalia config from previous install causes new Vidalia to hang
If a previous Vidalia install has created a vidalia.conf in the local application data folder it will contain a control port setting that will not connect to the VM instance of Tor. Tor VM should detect if the existing vidalia.conf needs to be replaced with a Tor VM default.
The manual work around is to move the %LOCALAPPDATA%\Vidalia\vidalia.conf elsewhere and restart.
EDIT: fixed; to be included in 0.0.2
[Automatically added by flyspray2trac: Operating System: All]