Re: [tor-bugs] #26520 [Applications/Tor Browser]: NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#26520: NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:
                                                 |  pospeselr
     Type:  defect                               |         Status:
                                                 |  needs_information
 Priority:  High                                 |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201808,      |  Actual Points:
  noscript                                       |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by rustybird):

 Replying to [comment:17 intrigeri]:
 > Replying to [comment:16 rustybird]:
 > > And the `Could not establish connection. Receiving end does not
 exist.` error from `ExtensionCommon.jsm` still appeared when you observed
 working JS?
 >
 > Yes (I've just tested again just to be sure).

 I tried it out with `tails-amd64-feature_15803-tor-browser-8.0a10+force-
 all-tests-3.9-20180819T1720Z-575956dc62+testing@xxxxxxxxxxxxxx`
 (apparently deleted from https://nightly.tails.boum.org/ in the meantime):

 Torbutton 2.0.2 from Tor Browser 8.0a10 does not have the `initialized =
 true`
 [https://gitweb.torproject.org/torbutton.git/commit/?id=aa379dcc5c06ee542a1c63adc769678700e32eaa
 fix] yet, so `sendMessage()` happens to be called twice on init. The first
 time it fails with the error message, the second time it succeeds for me.
 Same as you, apparently. Maybe my old test notebook causes delays in just
 the right order before the second `sendMessage()`, giving NoScript time to
 become ready? Whereas with vanilla 8.0a10 in my Fedora 28 test VM, both
 `sendMessage()` calls fail and I see the error twice.

 With the Torbutton fix (included in Torbutton >= 2.0.4), the bug does seem
 to consistently affect Tails in my testing.

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs