Opened 7 years ago

Closed 14 months ago

#6722 closed defect (wontfix)

Vidalia shouldn't warn about control socket not being connected after hitting "Stop Tor"

Reported by: karsten Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version: Vidalia: 0.2.20
Severity: Normal Keywords: archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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".

Child Tickets

Change History (2)

comment:1 Changed 21 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 14 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.