tor-launcher issueshttps://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues2020-06-27T13:42:20Zhttps://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20890Increase connection timeout to avoid "Could not connect to Tor control port" ...2020-06-27T13:42:20ZTracIncrease connection timeout to avoid "Could not connect to Tor control port" errorsI am on Windows 8.1 x64, not running an anti-virus app, or the firewall.
I have Tor 6.0.7
it was working fine, but something I have error "Could not connect to Tor control port"
Tried install new Tor in another folder and fine work, but ...I am on Windows 8.1 x64, not running an anti-virus app, or the firewall.
I have Tor 6.0.7
it was working fine, but something I have error "Could not connect to Tor control port"
Tried install new Tor in another folder and fine work, but after some time I get the same error message.
I tried
Start a Command Prompt (cmd.exe) and cd to Tor Browser\Browser (the folder that contains firefox.exe).
At the command prompt, type: firefox -console -jsconsole
And nothing. Nothing error logs, but Tor not running and I get same error message.
After shutdown system Tor fine work. But after some time, after close and reopen Tor window I get same error - "could not connect to Tor control port"
**Trac**:
**Username**: torrc591https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20761Tor Browser 6.5a4 is ignoring additional SocksPorts2020-06-27T13:42:20ZGeorg KoppenTor Browser 6.5a4 is ignoring additional SocksPortsLet's assume you have something like that in your torrc-defaults file in Tor Browser:
```
SocksPort 9150 IPv6Traffic PreferIPv6 KeepAliveIsolateSOCKSAuth
SocksPort 9160 IPv6Traffic PreferIPv6 KeepAliveIsolateSOCKSAuth
ControlPort 9151
Co...Let's assume you have something like that in your torrc-defaults file in Tor Browser:
```
SocksPort 9150 IPv6Traffic PreferIPv6 KeepAliveIsolateSOCKSAuth
SocksPort 9160 IPv6Traffic PreferIPv6 KeepAliveIsolateSOCKSAuth
ControlPort 9151
CookieAuthentication 1
```
And let's say you point your Torbirdy to 9160. That setup works perfectly fine with Tor Browser 6.5a3 and breaks with 6.5a4. Setting `extensions.torlauncher.socks_port_use_ipc` to `false` (trying to simulate the old behavior) does not fix it. Nor does setting `TOR_SOCKS_PORT=9150` help. In fact, looking at the code it seems this is not supported anymore which we should fix.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20678Uplift patches to maint-0.2.92020-06-27T13:42:20ZArlo BreaultUplift patches to maint-0.2.9It would be helpful to have these in the stable releases,
https://gitweb.torproject.org/tor-launcher.git/commit/?id=985b87cb1c6e6e0d70adb9279232423bd105eb4f
https://gitweb.torproject.org/tor-launcher.git/commit/?id=44c1cc246e8736e88906c...It would be helpful to have these in the stable releases,
https://gitweb.torproject.org/tor-launcher.git/commit/?id=985b87cb1c6e6e0d70adb9279232423bd105eb4f
https://gitweb.torproject.org/tor-launcher.git/commit/?id=44c1cc246e8736e88906c74058f2c582aa6178edhttps://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20468TorBrowser using a secert HASHEDPASSWORD2020-06-27T13:42:20ZcypherpunksTorBrowser using a secert HASHEDPASSWORDFor security reasons, I was trying force the TorBrowser to work with it's own tor instance (and SocksPort) but without allowing it to have access to the ControlPort.
I don't care for the TorButton New Identity or circuit path display fe...For security reasons, I was trying force the TorBrowser to work with it's own tor instance (and SocksPort) but without allowing it to have access to the ControlPort.
I don't care for the TorButton New Identity or circuit path display features.
I tried setting CookieAuthentication to 0 in torrc-defaults. But was surprised to find that the TorBrowser still managed to authenticate with the control port and the TorButton was able to display the circuit path.
With the help of the folks on irc, we were able to determine that the TorLauncher uses it's own secret hashed password if it's unable to find a cookie or env password.
Protocolinfo says: 250-AUTH METHODS=HASHEDPASSWORD
I think the TorBrowser and TorLauncher should respect the users wishes and not set a secret password for itself. Instead just work without the ControlPort.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20429TOR_SKIP_LAUNCH=1: progress window stays open2020-06-27T13:42:21ZMark SmithTOR_SKIP_LAUNCH=1: progress window stays openIf you run tor separately and use TOR_SKIP_LAUNCH=1 to start Tor Browser, Tor Launcher opens its progress window after you make changes via Tor Network Settings window. The progress window never makes any progress, and if you cancel it t...If you run tor separately and use TOR_SKIP_LAUNCH=1 to start Tor Browser, Tor Launcher opens its progress window after you make changes via Tor Network Settings window. The progress window never makes any progress, and if you cancel it tor is left in the DisableNetwork=1 state.
Kathy and I do not think the progress window should open in this situation. It looks like the code is confused by checking to see whether the bootstrap process has finished (in this case Tor Launcher thinks it has not finished, but really it has no idea).https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20321Quit Tor Browser Menu Option Does Not Work from Launcher on Mac OS2022-03-16T21:59:49ZcypherpunksQuit Tor Browser Menu Option Does Not Work from Launcher on Mac OSTorBrowser 6.0.5 on OS X 10.11.6.
When the "Tor Network Settings" dialog to Connect to the Tor Network is the only TorBrowser window open, the "Quit Tor Browser" option from the OS X Finder Tor Browser menu does not quit the application...TorBrowser 6.0.5 on OS X 10.11.6.
When the "Tor Network Settings" dialog to Connect to the Tor Network is the only TorBrowser window open, the "Quit Tor Browser" option from the OS X Finder Tor Browser menu does not quit the application.
To reproduce:
1. Disable network to force Tor Network Settings to open.
2. Open TorBrowser. The Tor Network Settings page should show with an error saying it is not connected to the Tor Network.
3. Now try closing the application from "Quit Tor Browser" in the Finder menu.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20315Tor launcher doesn't respect ReachableAddresses2022-03-16T22:00:38ZcypherpunksTor launcher doesn't respect ReachableAddressesOn a fresh copy of tor browser, any included ReachableAddresses rules are removed when the torrc file is overwritten by the tor launcher.On a fresh copy of tor browser, any included ReachableAddresses rules are removed when the torrc file is overwritten by the tor launcher.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20076Tor data directory permissions are too permissive on OS X2020-06-27T13:42:21ZGeorg KoppenTor data directory permissions are too permissive on OS XCurrently, OS X is the only platform where the Tor data directory needs to created by Tor Launcher. This happens via
```
f.create(f.DIRECTORY_TYPE, FileUtils.PERMS_DIRECTORY);
```
This boils down to `0755` which is too permissive for dir...Currently, OS X is the only platform where the Tor data directory needs to created by Tor Launcher. This happens via
```
f.create(f.DIRECTORY_TYPE, FileUtils.PERMS_DIRECTORY);
```
This boils down to `0755` which is too permissive for directories for the control socket.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/20075Tor Browser fails to start: FileUtils is undefined2020-06-27T13:42:21ZGeorg KoppenTor Browser fails to start: FileUtils is undefinedSince legacy/trac#14272 landed Tor Browser won't start if e.g. `torrc` needs to created as `FileUtils` is not defined in tl-util.jsm.Since legacy/trac#14272 landed Tor Browser won't start if e.g. `torrc` needs to created as `FileUtils` is not defined in tl-util.jsm.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/19957Don't wait for Tor to start2021-01-26T17:46:57ZbugzillaDon't wait for Tor to startIf communication between firefox.exe and tor.exe was intercepted for some reason during start, then
> The error message "Could not connect to Tor control port." is displayed after Tor Launcher (part of Tor Browser) fails to connect to th...If communication between firefox.exe and tor.exe was intercepted for some reason during start, then
> The error message "Could not connect to Tor control port." is displayed after Tor Launcher (part of Tor Browser) fails to connect to the Tor control port for 30 seconds.
But it usually happens when security suite asks users for permissions for these applications. And often 30 sec are not enough to create rules. So, Tor Launcher needs an option to manually continue the startup process instead of showing "Waiting for Tor to start...".https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/18543Change dialog message when there is no protocol to copy2022-03-16T22:06:25ZJens KubiezielChange dialog message when there is no protocol to copyI'm running Tor Browser 6.0a3-hardened on Debian GNU/Linux. When I wanted to Tor Browser, it showed me a message that Tor unexpectedly was closed. I wanted to copy the relevant log messages and clicked on the "copy the Tor protocol messa...I'm running Tor Browser 6.0a3-hardened on Debian GNU/Linux. When I wanted to Tor Browser, it showed me a message that Tor unexpectedly was closed. I wanted to copy the relevant log messages and clicked on the "copy the Tor protocol message" button (I use the german version which says "Tor-Protokoll in die Zwischenablage kopieren"). After I hit the button a message appeared which read like "Copy ready. 0 Messages were copied" (German: "Kopie vollständig. 0 Tor-Protokollnachrichten sind bereit …").
To me this message doesn't make fully sense. It says that there were 0 messages copied. IMHO it would be better to print something like "Currently there are no log messages to copy." or a similar message to make it clear that there are no log messages.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/18330Tor Launcher only accepts HEXDIGIT passwords for controller2022-03-16T22:09:30ZGeorg KoppenTor Launcher only accepts HEXDIGIT passwords for controllerWe currently give the advice to double quote the password for the Tor controller in the start-tor-browser script which seems to be a good thing given the trouble with quoting correctly. But this does not work (I wonder if it actually eve...We currently give the advice to double quote the password for the Tor controller in the start-tor-browser script which seems to be a good thing given the trouble with quoting correctly. But this does not work (I wonder if it actually ever worked). The problem is that Tor Launcher is expecting a `HEXDIGIT` password. Using `deadbeef` is fine but
```
password[i] = parseInt(aHexPassword.substr(i * 2, 2), 16);
```
does not like things like `test` or `'"test"'` and is e.g. reporting for the former `NaN, NaN` which breaks the hashed control password option (the argument `aHexPassword` is spoiling the bug hunt a bit but I was not affected by it :) ). That in turn breaks the authentication and Tor Browser won't start.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/18327Aborting the Tor Launcher setup wizard and restarting should show the languag...2022-03-16T22:10:27ZGeorg KoppenAborting the Tor Launcher setup wizard and restarting should show the language selection dialog againAborting the setup wizard does not lead to the language selection dialog showing up again on re-start. I think we should treat it as an integral part of the setup wizard, though, showing it again as well. For instance, it might be the ca...Aborting the setup wizard does not lead to the language selection dialog showing up again on re-start. I think we should treat it as an integral part of the setup wizard, though, showing it again as well. For instance, it might be the case that users realize they selected the wrong language and try to undo that by clicking on `Quit` on the next pane (as there is no `Back` button available). But restarting Tor Browser won't help them currently.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/18083Implement all Vidalia functionality in Firefox addons2020-06-27T13:42:22ZcypherpunksImplement all Vidalia functionality in Firefox addonsNow the addons lack the most of Vidalia functionality. I think if you chose to replace Vidalia with addons, the addons should allow anything which can be done with Vidalia.Now the addons lack the most of Vidalia functionality. I think if you chose to replace Vidalia with addons, the addons should allow anything which can be done with Vidalia.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/18069"General SOCKS server failure" prevents TBB launch2020-06-27T13:42:22ZTrac"General SOCKS server failure" prevents TBB launch1/15/2016 11:41:36 AM.600 [NOTICE] Bootstrapped 5%: Connecting to directory server
1/15/2016 11:42:06 AM.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 11:42:06 AM.400 [NOTICE] DisableNetwork is se...1/15/2016 11:41:36 AM.600 [NOTICE] Bootstrapped 5%: Connecting to directory server
1/15/2016 11:42:06 AM.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 11:42:06 AM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:42:06 AM.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 11:42:06 AM.600 [NOTICE] Delaying directory fetches: DisableNetwork is set.
1/15/2016 11:42:49 AM.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:42:49 AM.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:42:49 AM.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:42:49 AM.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 11:42:56 AM.600 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
1/15/2016 11:42:56 AM.900 [WARN] Proxy Client: unable to connect to 104.131.108.182:56880 ("general SOCKS server failure")
1/15/2016 11:42:56 AM.900 [WARN] Proxy Client: unable to connect to 83.212.101.3:41213 ("general SOCKS server failure")
1/15/2016 11:42:56 AM.900 [WARN] Proxy Client: unable to connect to 109.105.109.165:24215 ("general SOCKS server failure")
1/15/2016 11:43:22 AM.000 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 11:43:22 AM.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:43:22 AM.000 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 11:43:37 AM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:43:37 AM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:43:37 AM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:43:37 AM.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 11:44:04 AM.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 11:44:04 AM.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:44:04 AM.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 11:44:04 AM.800 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 3; recommendation warn; host 4D6C0DF6DEC9398A4DEF07084F3CD395A96DD2AD at 0.0.1.0:1)
1/15/2016 11:44:04 AM.800 [WARN] 5 connections have failed:
1/15/2016 11:44:04 AM.800 [WARN] 3 connections died in state handshaking (proxy) with SSL state (No SSL object)
1/15/2016 11:44:04 AM.800 [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
1/15/2016 11:44:04 AM.800 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
1/15/2016 11:44:20 AM.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:44:20 AM.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:44:20 AM.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:44:20 AM.900 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 11:44:27 AM.000 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 11:44:27 AM.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 11:44:27 AM.000 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 11:44:27 AM.000 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 4; recommendation warn; host 46D4A71197B8FA515A826C6B017C522FE264655B at 0.0.2.0:1)
1/15/2016 11:44:27 AM.000 [WARN] 6 connections have failed:
1/15/2016 11:44:27 AM.000 [WARN] 3 connections died in state handshaking (proxy) with SSL state (No SSL object)
1/15/2016 11:44:27 AM.000 [WARN] 2 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
1/15/2016 11:44:27 AM.000 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
1/15/2016 13:23:30 PM.100 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 13:23:32 PM.000 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 13:23:32 PM.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:23:32 PM.000 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 13:39:46 PM.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:39:46 PM.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:39:46 PM.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:39:46 PM.700 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 13:39:47 PM.900 [WARN] Proxy Client: unable to connect to 148.251.233.72:80 ("invalid SOCKS 4 response code")
1/15/2016 13:39:47 PM.900 [WARN] Proxy Client: unable to connect to 124.6.36.195:443 ("invalid SOCKS 4 response code")
1/15/2016 13:40:32 PM.600 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 13:40:32 PM.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:40:32 PM.600 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 13:40:33 PM.500 [NOTICE] Delaying directory fetches: DisableNetwork is set.
1/15/2016 13:40:43 PM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:40:43 PM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:40:43 PM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:40:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 13:40:45 PM.700 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 13:40:45 PM.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:40:45 PM.700 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
1/15/2016 13:40:46 PM.500 [NOTICE] Delaying directory fetches: DisableNetwork is set.
1/15/2016 13:41:50 PM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:41:50 PM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:41:50 PM.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:41:50 PM.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/15/2016 13:42:01 PM.300 [WARN] Proxy Client: unable to connect to 60.63.97.221:443 ("general SOCKS server failure")
1/15/2016 13:42:01 PM.300 [WARN] Proxy Client: unable to connect to 87.237.118.139:444 ("general SOCKS server failure")
1/15/2016 13:42:01 PM.300 [WARN] Proxy Client: unable to connect to 60.16.182.53:9001 ("general SOCKS server failure")
1/15/2016 13:42:04 PM.700 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
1/15/2016 13:42:04 PM.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
1/15/2016 13:42:04 PM.700 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
**Trac**:
**Username**: johndoegreenevillehttps://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/17634Be more strict if applying double quotes around passwords2020-06-27T13:42:22ZGeorg KoppenBe more strict if applying double quotes around passwordsWhen authenticating we handle the control password as follows:
```
// Surround non-hex strings with double quotes.
const kIsHexRE = /^[A-Fa-f0-9]*$/;
if (!kIsHexRE.test(pwdArg))
pwdArg = '"' + pwdArg + '"';
```
But the spec says `"AUTHEN...When authenticating we handle the control password as follows:
```
// Surround non-hex strings with double quotes.
const kIsHexRE = /^[A-Fa-f0-9]*$/;
if (!kIsHexRE.test(pwdArg))
pwdArg = '"' + pwdArg + '"';
```
But the spec says `"AUTHENTICATE" [ SP 1*HEXDIG / QuotedString ] CRLF`
and `HEXDIG` being `DIGIT / "A" / "B" / "C" / "D" / "E" / "F"` according to RFC 2234. Thus, we are a bit more lenient than we should at the moment.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/17344language prompt should enumerate available langpacks2020-06-27T13:42:23ZMark Smithlanguage prompt should enumerate available langpacksIn legacy/trac#12967, we are adding a language prompt to Tor Launcher. In the current implementation, the list of available languages is hard-coded. We should instead enumerate the installed language packs and only show those languages. ...In legacy/trac#12967, we are adding a language prompt to Tor Launcher. In the current implementation, the list of available languages is hard-coded. We should instead enumerate the installed language packs and only show those languages. Perhaps we should also suppress the prompt if there is only one language to choose from.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/16753resize Tor Network Settings dialog to fit content2020-06-27T13:42:23ZMark Smithresize Tor Network Settings dialog to fit contentIn TB 5.5a1, Tor Launcher's "Tor Network Settings" window does not lay out nicely, at least on Mac OS. Presumably this is due to the combination of new fonts and the fixed width of that window.In TB 5.5a1, Tor Launcher's "Tor Network Settings" window does not lay out nicely, at least on Mac OS. Presumably this is due to the combination of new fonts and the fixed width of that window.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/15704network is not disabled when wizard is shown if default bridges are configured2020-06-27T13:42:23ZMark Smithnetwork is not disabled when wizard is shown if default bridges are configuredIf default bridges are configured and the network settings wizard is opened during a subsequent launch of Tor Browser, bootstrapping proceeds while the wizard is open. This problem occurs because the code in Tor Launcher that configures...If default bridges are configured and the network settings wizard is opened during a subsequent launch of Tor Browser, bootstrapping proceeds while the wizard is open. This problem occurs because the code in Tor Launcher that configures default bridges also unconditionally sets DisableNetwork=0.
Kathy and I found this problem while testing a fix for legacy/trac#11879.https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/14923Tor Launcher should have accessibility support.2022-02-03T14:54:16ZSheriefTor Launcher should have accessibility support.A couple of users with poor sight complained that Tor Launcher doesn't support voice-over software which can be a problem.A couple of users with poor sight complained that Tor Launcher doesn't support voice-over software which can be a problem.