#22266: fix the jump-to-80% issue -----------------------------------------------+--------------------------- Reporter: catalyst | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Tor: | 0.3.3.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: usability, ux, ux-team, bootstrap | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------------------------+--------------------------- Changes (by mcs):
* status: needs_information => new Comment: Replying to [comment:12 catalyst]: > The controller-visible bootstrap phase always starts from 0 when tor starts up (even if DisableNetwork is 1, I think); phase 0 is always the first bootstrap event sent to the control connection. The trigger for reaching phase 80 is having a consensus (though not necessarily an up-to- date-one; this is probably a bug!) and enough descriptors to build circuits. This might not happen immediately upon setting DisableNetwork=0.... Thanks for the detailed explanation. Given what you said, I think it is fine for Tor Launcher to show a progress bar at position zero when that is tor's internal state. The scenario that bothered people in the Linda/Berkeley study is still addressed by the fix in #23240 (wherein Tor Launcher retrieves the current status before showing the progress bar). -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22266#comment:14> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs