[tor-bugs] #6722 [Vidalia]: Vidalia shouldn't warn about control socket not being connected after hitting "Stop Tor"
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Wed Aug 29 06:31:06 UTC 2012
#6722: Vidalia shouldn't warn about control socket not being connected after
hitting "Stop Tor"
---------------------+------------------------------------------------------
Reporter: karsten | Owner: chiiph
Type: defect | Status: new
Priority: normal | Milestone:
Component: Vidalia | Version: Vidalia: 0.2.20
Keywords: | Parent:
Points: | Actualpoints:
---------------------+------------------------------------------------------
When I start the TBB and hit "Stop Tor" a second later (because I want to
configure bridges), Vidalia tells me a few seconds later: "Vidalia was
unable to register for some events. Many of Vidalia's features may be
unavailable. Control socket is not connected."
That message will confuse most users who don't know what an event is and
why we would want to register for them.
But that message could also easily be suppressed by checking if Tor is
supposed to be running or not.
The even better would be to stop the thread that tries to connect to Tor
when the user hits "Stop Tor".
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6722>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list