[tor-bugs] #28140 [Core Tor/Tor]: Our circuit died due to an invalid selected path if switching to plugabble transports

[Tor Bug Tracker & Wiki]

#28140: Our circuit died due to an invalid selected path if switching to plugabble
transports
----------------------------------+------------------------------------
 Reporter:  gk                    |          Owner:  (none)
     Type:  defect                |         Status:  needs_information
 Priority:  High                  |      Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor          |        Version:  Tor: 0.3.2.7-rc
 Severity:  Normal                |     Resolution:
 Keywords:  tor-path, regression  |  Actual Points:
Parent ID:                        |         Points:
 Reviewer:                        |        Sponsor:
----------------------------------+------------------------------------

Comment (by essentially):

 Replying to [ticket:28140 gk]:
 > This makes Tor Browser essentially unusable until one changes settings
 again or restarts.
 Unfortunately, this breaks the most common browsing experience (plain tor
 w/o bridges, WiFi network).
 Neither changing settings to obfs4, nor switching back can help.
 Killing tor process manually when obfs4proxy process is already running
 leads to tor process is unable to boot and exits immediately (config is
 default, switched from obfs4). Killing obfs4proxy process helps, but tor
 launcher got stuck at 80% for about a minute (no CPU or network activity),
 so it's hard to realize it's booting.
 After all, the circuit display disappeared after the tor restart :(

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28140#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online