Feature #5840

Do not restart Vidalia on network reconnect

Added by Tails 2013-07-18 07:47:02 . Updated 2016-07-21 12:48:54 .

Status:
Rejected
Priority:
Low
Assignee:
Category:
Tor configuration
Target version:
Start date:
2014-07-19
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Due to Vidalia’s Vidalia bug 2150, we restart Vidalia after network reconnection.

Note that we now only start Tor once the network is up, so only _re_connection to the network is affected. So, the other potential place to fix the bug (Tor bug 1247 is not an option anymore.

Subtasks

Feature #7614: Have Vidalia automatically (re-)connect to a Tor instance started after startup Rejected

0

History

#1 Updated by intrigeri 2013-10-04 05:59:56

  • Subject changed from dont restart vidalia on network reconnect to Do not restart Vidalia on network reconnect
  • Starter set to No

#2 Updated by intrigeri 2014-07-19 16:38:44

  • Description updated
  • Category set to Tor configuration
  • Type of work changed from Upstream to Code

#3 Updated by BitingBird 2015-02-05 20:57:33

We’re planning on removing Vidalia, so I think this should be rejected (better to work on the replacement).

#4 Updated by BitingBird 2015-03-05 13:02:02

  • Affected tool set to Vidalia

#5 Updated by intrigeri 2015-05-18 13:43:29

Thanks to https://trac.torproject.org/projects/tor/ticket/8766 being fixed in Tor 0.2.7-alpha-1, we might be able to stop restarting Tor (and in turn, Vidalia) after we fix the system time.

#6 Updated by BitingBird 2015-08-25 11:51:36

  • Status changed from Confirmed to Rejected

Vidalia will be replaced by TorMonitor -> let’s not work on that anymore :)

#7 Updated by intrigeri 2016-07-21 12:48:54

  • Affected tool deleted (Vidalia)