Opened 8 years ago
Closed 8 months ago
#2150 closed defect (wontfix)
Autoconnect to a tor instance loaded after startup
Reported by: | T(A)ILS developers | Owned by: | chiiph |
---|---|---|---|
Priority: | Medium | Milestone: | |
Component: | Archived/Vidalia | Version: | Vidalia 0.2.10 |
Severity: | Normal | Keywords: | archived-closed-2018-07-04 |
Cc: | anonym, intrigeri | Actual Points: | |
Parent ID: | #1247 | Points: | |
Reviewer: | Sponsor: |
Description
Context
In Debian systems, Tor is launched as a daemon, which has its own user. Vidalia then connects to Tor through the control port.
Steps to reproduce the problem
- Start Vidalia
- (Re-)start the Tor daemon, e.g. a by a script triggered because the system got a new connection (this restart is required due to a tor bug #1247)
Expected result
Vidalia (re-)connects to the Tor daemon.
Actual result
Vidalia says that "Tor is not running"
Workaround
The user need to click on "Start Tor" after the daemon restart.
Child Tickets
Change History (6)
comment:1 Changed 8 years ago by
Parent ID: | → #1247 |
---|---|
Type: | enhancement → defect |
Version: | → Vidalia 0.2.10 |
comment:2 Changed 8 years ago by
comment:3 Changed 8 years ago by
Cc: | amnesia@… added |
---|
comment:4 Changed 5 years ago by
Cc: | anonym intrigeri added; amnesia@… removed |
---|
comment:5 Changed 15 months ago by
Severity: | → Normal |
---|
Set all open tickets without a severity to "Normal"
comment:6 Changed 8 months ago by
Keywords: | archived-closed-2018-07-04 added |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Close all tickets in archived components
Note: See
TracTickets for help on using
tickets.
Linux Mandriva 2010.2 32 bit
kde 4.5.5
qt 4.7.1
vidalia 0.2.9
same pb
tor is set up separately inde pendantly.
it's a daemon started by the system when you start the pc
and the owner of tor is "toruser" user with "toruser" group, not the current user
which uses vidalia