Opened 11 years ago

Closed 9 years ago

#945 closed defect (fixed)

Vidalia config from previous install causes new Vidalia to hang

Reported by: coderman Owned by: coderman
Priority: Low Milestone:
Component: Archived/Tor VM Version: 0.2.1.12-alpha
Severity: Keywords:
Cc: coderman Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by karsten)

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]

Child Tickets

Change History (2)

comment:1 in reply to:  description Changed 9 years ago by karsten

Component: Tor VMVidalia
Description: modified (diff)

Replying to coderman:

EDIT: fixed; to be included in 0.0.2

Can this ticket be closed as fixed?

comment:2 Changed 9 years ago by Sebastian

Component: VidaliaTor VM
Resolution: Nonefixed
Status: assignedclosed

I don't believe this is a Vidalia issue, as it appears to be related to some Tor VM specific paths. Since coderman claimed that this was fixed, and given Tor VM's current state, I'm going to close this. Reopen if necessary.

Note: See TracTickets for help on using tickets.