Opened 11 years ago

Closed 10 years ago

#1186 closed defect (fixed)

Startup "non-tor" doesn't work...

Reported by: JofCore Owned by:
Priority: Low Milestone:
Component: Applications/Torbutton Version: 1.2.3
Severity: Keywords:
Cc: JofCore Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by mikeperry)

I would like my browser to always start up with Tor / Torbutton disabled, regardless of how the browser was shut down.
I usually disable Tor / Torbutton before I exit my browser, but occasionally I forget, so I'd like it if it automatically
was disabled on startup of the browser.

There is an option under Security Settings -> Startup that seems to be aimed at what I would like, but for some reason it
doesn't appear to work properly for me.

I have my setting currently set to:

On normal startup, set Tor state to: Non-Tor
On session restored startup, set Tor state to: Non-Tor

However, if I close my browser w/out first clicking tor / torbutton off and then restart my browser, the Tor status is
still set to disabled, which seems to be contrary to how my settings are set.

Am I missing something or is this feature not working properly? Does anyone else have this issue or am I doing
something wrong?


[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (4)

comment:1 Changed 10 years ago by mikeperry

It sounds like you have the setting backwards. To start in Tor mode, you want your startup to be "Tor" not "Non-Tor".

Or was this a typo?

Also, which firefox and torbutton versions?

comment:2 Changed 10 years ago by JofCore

I think you misunderstood... I wanted my browser to always default to Tor being off when I started it up, and this wasn't happening. However, it seems this has been fixed in a later version of Tor...? I'm currently using 1.2.4, and I tested this again and it's working now as it should :) I don't remember what version I was using (should've put that in the original post, sorry); but I do know that I've updated since the original post so it looks like the issue has been fixed!

Thanx for your reply!

comment:3 Changed 10 years ago by JofCore

ah, I see in my original post that it says "reported version: 1.2.3" so it looks like it was an earlier version :)

comment:4 Changed 10 years ago by mikeperry

Description: modified (diff)
Resolution: Nonefixed
Status: newclosed
Note: See TracTickets for help on using tickets.