Custom Query (14157 matches)
Results (16 - 18 of 14157)
|#2008||duplicate||"Circuit Build Times Network Close" warnings||xebulba|
Oct 04 11:36:31.905 [Warning] circuit_build_times_network_close(): Bug: Circuit somehow completed a hop while the network was not live. Network was last live at 2010-10-04 11:35:30, but circuit launched at 2010-10-04 11:35:30. It's now 2010-10-04 11:36:31.
Oct 04 12:06:13.958 [Warning] circuit_build_times_network_close(): Bug: Circuit somehow completed a hop while the network was not live. Network was last live at 2010-10-04 12:05:12, but circuit launched at 2010-10-04 12:05:12. It's now 2010-10-04 12:06:13.
|#16832||duplicate||"Circuit on detached list which I had no reason to mark"||tmpname0901|
Tor v0.2.6.10 running on CentOS6/x86_64. Relay is a middle node, and has this entry in its log file:
Aug 16 11:19:38.000 [warn] circuit_unlink_all_from_channel(): Bug: Circuit on detached list which I had no reason to mark
|#7514||wontfix||"Configure controlport automatically" is mysteriously missing when Vidalia couldn't start Tor||chiiph||arma|
When a Windows user is running Tor already and starts TBB, it fails to start Tor because Tor can't bind to 9050 / 9051. When this happens, Vidalia chooses not to display the "Configure controlport automatically" button on its Settings -> Advanced page.
The workaround for people who want to run multiple Tors is "close all your other Tors before starting TBB, and then tell TBB to switch to switch to auto". It would be good if Vidalia could handle this directly though -- i.e. if it failed to start Tor, still offer the option to switch Tor to auto.
A simpler approach that would still help here would be to leave the clickbox in, but grey it out if you don't want the user clicking it.