Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T00:42:48Zhttps://gitlab.torproject.org/legacy/trac/-/issues/24614update to a newer Meek tag2020-06-16T00:42:48ZKathleen Bradeupdate to a newer Meek tagTor Launcher will soon require TOR_PT_EXIT_ON_STDIN_CLOSE support in Meek which will require us to move to Meek 0.28 tag.
This is needed for Moat integration.Tor Launcher will soon require TOR_PT_EXIT_ON_STDIN_CLOSE support in Meek which will require us to move to Meek 0.28 tag.
This is needed for Moat integration.Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/25087Snowflake broken if no libatomic on host (e.g. Lubuntu 17 64 bits)2020-06-16T00:43:42ZcypherpunksSnowflake broken if no libatomic on host (e.g. Lubuntu 17 64 bits)Logs/
```
Jan 30 10:45:02.000 [notice] Opening Socks listener on 127.0.0.1:9150
Jan 30 10:45:03.000 [warn] The communication stream of managed proxy './TorBrowser/Tor/PluggableTransports/snowflake-client' is 'closed'. Most probably the ...Logs/
```
Jan 30 10:45:02.000 [notice] Opening Socks listener on 127.0.0.1:9150
Jan 30 10:45:03.000 [warn] The communication stream of managed proxy './TorBrowser/Tor/PluggableTransports/snowflake-client' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
Jan 30 10:45:04.000 [notice] Bootstrapped 5%: Connecting to directory server
Jan 30 10:45:04.000 [warn] We were supposed to connect to bridge '0.0.3.0:1' using pluggable transport 'snowflake', but we can't find a pluggable transport proxy supporting 'snowflake'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
Jan 30 10:45:04.000 [warn] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn; host 2B280B23E1107BB62ABFC40DDCC8824814F80A72 at 0.0.3.0:1)
Jan 30 10:45:04.000 [notice] Closing no-longer-configured Socks listener on 127.0.0.1:9150
Jan 30 10:45:04.000 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
Jan 30 10:45:04.000 [notice] Closing old Socks listener on 127.0.0.1:9150
Jan 30 10:45:36.000 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
```https://gitlab.torproject.org/legacy/trac/-/issues/25134Import strings from all locales in torbutton import-translations.sh2020-06-16T01:28:11ZArthur EdelsteinImport strings from all locales in torbutton import-translations.shI have been looking at how to add more locales to Tor Browser and I noticed that tor-launcher.git and torbutton.git handle translations differently. In tor-launcher, the script `import-translations.sh` imports new strings from all locale...I have been looking at how to add more locales to Tor Browser and I noticed that tor-launcher.git and torbutton.git handle translations differently. In tor-launcher, the script `import-translations.sh` imports new strings from all locales provided by Transifex, not just the ones deploy in Tor Browser. But in torbutton, `import-translations.sh` we are only importing strings from a specific list of locales and ignoring the rest. I would suggest we should change torbutton to import all locales, because then:
* We won't have to keep a list of locales in torbutton sync'd with Tor Browser.
* It will potentially facilitate building a multi-local Tor Browser.