[tor-bugs] #32328 [Applications/Tor Browser]: red screen of death

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Nov 3 06:05:39 UTC 2019


#32328: red screen of death
--------------------------------------+-----------------------------------
 Reporter:  qwertyu                   |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_information
 Priority:  Immediate                 |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Critical                  |     Resolution:
 Keywords:                            |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------

Comment (by liziqsj):

 Replying to [comment:1 gk]:
 > Do you get this every time you open Tor Browser? How did you set up Tor
 Browser? Is it the default version downloaded from our website,
 unmodified? Which operating system are you on?

 I'm not the OP, I have similar problem
 I'm random get such prompt, TBB version:9.0 (based on Mozilla Firefox
 68.2.0esr) (32-bit), Linux system.
 My log:

 {{{
 11/3/19, 05:40:30.320 [NOTICE] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 11/3/19, 05:40:30.320 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 11/3/19, 05:40:30.320 [NOTICE] Opened Socks listener on 127.0.0.1:9150
 11/3/19, 05:40:31.240 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to
 pluggable transport
 11/3/19, 05:40:31.241 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected
 to pluggable transport
 11/3/19, 05:40:31.459 [NOTICE] Bridge 'Lisbeth' has both an IPv4 and an
 IPv6 address.  Will prefer using its IPv6 address
 ([2001:470:b381:bfff:216:3eff:fe23:d6c3]:443) based on the configured
 Bridge address.
 11/3/19, 05:40:56.228 [WARN] Proxy Client: unable to connect to
 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
 11/3/19, 05:40:56.844 [NOTICE] Bootstrapped 10% (conn_done): Connected to
 a relay
 11/3/19, 05:40:57.229 [NOTICE] Bootstrapped 14% (handshake): Handshaking
 with a relay
 11/3/19, 05:40:57.623 [NOTICE] Bootstrapped 15% (handshake_done):
 Handshake with a relay done
 11/3/19, 05:40:57.624 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded
 enough directory info to build circuits
 11/3/19, 05:40:58.780 [NOTICE] Bootstrapped 95% (circuit_create):
 Establishing a Tor circuit
 11/3/19, 05:40:58.498 [NOTICE] new bridge descriptor 'smallerRichard'
 (fresh): $FB70B257C162BF1038CA669D568D76F5B7F0BABB~smallerRichard at
 144.217.20.138
 11/3/19, 05:40:59.820 [NOTICE] new bridge descriptor 'cymrubridge31'
 (fresh): $C8CBDB2464FC9804A69531437BCF2BE31FDD2EE4~cymrubridge31 at
 38.229.1.78
 11/3/19, 05:40:59.146 [NOTICE] new bridge descriptor 'griinchux' (fresh):
 $011F2599C0E9B27EE74B353155E244813763C3E5~griinchux at 85.31.186.98
 11/3/19, 05:40:59.384 [NOTICE] new bridge descriptor 'cymrubridge33'
 (fresh): $0BAC39417268B96B9F514E7F63FA6FBA1A788955~cymrubridge33 at
 38.229.33.83
 11/3/19, 05:40:59.736 [NOTICE] new bridge descriptor 'zipfelmuetze'
 (fresh): $91A6354697E6B02A386312F68D82CF86824D3606~zipfelmuetze at
 85.31.186.26
 11/3/19, 05:40:59.737 [NOTICE] Bootstrapped 100% (done): Done
 11/3/19, 05:41:03.684 [NOTICE] New control connection opened from
 127.0.0.1.
 11/3/19, 05:41:03.684 [NOTICE] New control connection opened from
 127.0.0.1.
 11/3/19, 05:41:12.717 [NOTICE] Bridge 'Lisbeth' has both an IPv4 and an
 IPv6 address.  Will prefer using its IPv6 address
 ([2001:470:b381:bfff:216:3eff:fe23:d6c3]:443) based on the configured
 Bridge address.
 11/3/19, 05:41:12.748 [WARN] Proxy Client: unable to connect to
 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
 11/3/19, 05:41:14.562 [NOTICE] Bridge 'Lisbeth' has both an IPv4 and an
 IPv6 address.  Will prefer using its IPv4 address (192.95.36.142:443)
 based on the configured Bridge address.
 11/3/19, 05:41:16.220 [WARN] Proxy Client: unable to connect to
 216.252.162.21:46089 ("general SOCKS server failure")
 11/3/19, 05:41:16.220 [WARN] Proxy Client: unable to connect to
 193.11.166.194:27015 ("general SOCKS server failure")
 11/3/19, 05:41:16.223 [WARN] Proxy Client: unable to connect to
 37.218.245.14:38224 ("general SOCKS server failure")
 11/3/19, 05:41:16.226 [WARN] Proxy Client: unable to connect to
 37.218.240.34:40035 ("general SOCKS server failure")
 11/3/19, 05:41:16.226 [WARN] Proxy Client: unable to connect to
 193.11.166.194:27025 ("general SOCKS server failure")
 11/3/19, 05:41:16.226 [WARN] Proxy Client: unable to connect to
 193.11.166.194:27020 ("general SOCKS server failure")
 11/3/19, 05:41:16.909 [NOTICE] new bridge descriptor 'Lisbeth' (fresh):
 $CDF2E852BF539B82BD10E27E9115A31734E378C2~Lisbeth at 192.95.36.142
 11/3/19, 05:44:31.955 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:80. Giving up. (waiting for circuit)
 11/3/19, 05:44:51.369 [WARN] Proxy Client: unable to connect to
 38.229.33.83:80 ("general SOCKS server failure")
 11/3/19, 05:45:58.767 [WARN] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 11/3/19, 05:45:58.767 [NOTICE] Our circuit 0 (id: 59) died due to an
 invalid selected path, purpose General-purpose client. This may be a torrc
 configuration issue, or a bug.
 11/3/19, 05:46:52.980 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:80. Giving up. (waiting for circuit)
 11/3/19, 05:47:58.115 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:80. Giving up.
 11/3/19, 05:48:18.121 [WARN] Proxy Client: unable to connect to
 192.95.36.142:443 ("general SOCKS server failure")
 }}}

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


More information about the tor-bugs mailing list