[tor-bugs] #4031 [Tor Browser]: Firefox fails to find SOCKS proxy after tor is restarted through Vidalia

[Tor Bug Tracker & Wiki]

#4031: Firefox fails to find SOCKS proxy after tor is restarted through Vidalia
-------------------------+--------------------------------------------------
 Reporter:  rpw          |          Owner:  mikeperry
     Type:  defect       |         Status:  new      
 Priority:  normal       |      Milestone:           
Component:  Tor Browser  |        Version:           
 Keywords:               |         Parent:           
   Points:               |   Actualpoints:           
-------------------------+--------------------------------------------------
 The Tor Browser Bundle version 2.2.34-4 on Linux uses the SocksPort auto
 setting in torrc. After restarting tor through the Vidalia interface, a
 new control port and a new SOCKS port are chosen while Firefox still uses
 the old SOCKS port. This causes "Connection refused" errors in Firefox.

 Steps to reproduce:

 1) Start Tor browser bundle
 2) Random browsing
 2) Click "Stop Tor" button in Vidalia Control Panel
 3) Click "Start Tor" button in Vidalia Control Panel
 4) Open any URL

 Expected result: URL can be opened normally
 Actual result: "Connection refused" error message

 Suggestion for the fix on #tor-dev was:

 !00:42 < armadev> vidalia could also fix it by memorizing the socks and
 control port (it does this anyway so it can tell firefox when it launches
 it),
 !00:42 < armadev> and restarting tor with the same ports it picked the
 first time

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4031>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online