Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:52:29Zhttps://gitlab.torproject.org/legacy/trac/-/issues/33686Tor 0.4.2.7 wont get past bootstrap phase with Sandbox 1 enabled2020-06-13T15:52:29ZcypherpunksTor 0.4.2.7 wont get past bootstrap phase with Sandbox 1 enabledI get this output from the terminal only when Sandbox 1 is enabled and it did not happen on earlier versions:
Mar 21 21:07:21.000 [notice] Bootstrapped 0% (starting): Starting
Mar 21 21:10:10.000 [notice] Starting with guard context "...I get this output from the terminal only when Sandbox 1 is enabled and it did not happen on earlier versions:
Mar 21 21:07:21.000 [notice] Bootstrapped 0% (starting): Starting
Mar 21 21:10:10.000 [notice] Starting with guard context "default"
Mar 21 21:10:10.000 [warn] tor_bug_occurred_(): Bug: src/lib/evloop/workqueue.c:353: workerthread_new: This line should not have been reached. (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: Tor 0.4.2.7: Line unexpectedly reached at workerthread_new at src/lib/evloop/workqueue.c:353. Stack trace: (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(log_backtrace_impl+0x47) [0x600404] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_bug_occurred_+0xa9) [0x5fcea2] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(threadpool_new+0x12b) [0x5ae6b0] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(cpu_init+0x59) [0x4be66e] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(run_tor_main_loop+0x9f) [0x4b3064] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_run_main+0xb85) [0x4b3f16] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_main+0x23) [0x4b1f98] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(main+0x13) [0x4b1c24] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x97) [0xb694b524] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [err] Can't launch worker thread.
Mar 21 21:10:10.000 [warn] tor_bug_occurred_(): Bug: src/lib/evloop/workqueue.c:519: threadpool_start_threads: This line should not have been reached. (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: Tor 0.4.2.7: Line unexpectedly reached at threadpool_start_threads at src/lib/evloop/workqueue.c:519. Stack trace: (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(log_backtrace_impl+0x47) [0x600404] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_bug_occurred_+0xa9) [0x5fcea2] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(threadpool_new+0x15b) [0x5ae6e0] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(cpu_init+0x59) [0x4be66e] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(run_tor_main_loop+0x9f) [0x4b3064] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_run_main+0xb85) [0x4b3f16] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_main+0x23) [0x4b1f98] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(main+0x13) [0x4b1c24] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x97) [0xb694b524] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] tor_bug_occurred_(): Bug: src/lib/evloop/workqueue.c:563: threadpool_new: This line should not have been reached. (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: Tor 0.4.2.7: Line unexpectedly reached at threadpool_new at src/lib/evloop/workqueue.c:563. Stack trace: (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(log_backtrace_impl+0x47) [0x600404] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_bug_occurred_+0xa9) [0x5fcea2] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(threadpool_new+0x183) [0x5ae708] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(cpu_init+0x59) [0x4be66e] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(run_tor_main_loop+0x9f) [0x4b3064] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_run_main+0xb85) [0x4b3f16] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(tor_main+0x23) [0x4b1f98] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: tor(main+0x13) [0x4b1c24] (on Tor 0.4.2.7 )
Mar 21 21:10:10.000 [warn] Bug: /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x97) [0xb694b524] (on Tor 0.4.2.7 )
============================================================ T= 1584825010
Tor 0.4.2.7 died: Caught signal 11
tor(+0x19631a)[0x60031a]
tor(threadpool_register_reply_event+0x19)[0x5ae80e]
tor(threadpool_register_reply_event+0x19)[0x5ae80e]
tor(cpu_init+0x61)[0x4be676]
tor(run_tor_main_loop+0x9f)[0x4b3064]
tor(tor_run_main+0xb85)[0x4b3f16]
tor(tor_main+0x23)[0x4b1f98]
tor(main+0x13)[0x4b1c24]
/lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x97)[0xb694b524]
[1]+ Illegal instruction tor -f torrcTor: 0.4.4.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/33757Fix log message when multiple tors try the same data directory2020-06-13T15:52:37ZteorFix log message when multiple tors try the same data directoryWhen a user launches two tor processes in the same data directory, they get these confusing logs:
```
Mar 29 17:45:08.000 [warn] It looks like another Tor process is running with the same data directory. Waiting 5 seconds to see if it g...When a user launches two tor processes in the same data directory, they get these confusing logs:
```
Mar 29 17:45:08.000 [warn] It looks like another Tor process is running with the same data directory. Waiting 5 seconds to see if it goes away.
Mar 29 17:45:13.000 [err] No, it's still there. Exiting.
Mar 29 17:45:13.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.4.2.7 )
Mar 29 17:45:13.000 [err] Reading config failed--see warnings above.
Mar 29 19:55:41.000 [notice] Catching signal TERM, exiting cleanly.
```
Full logs:
https://lists.torproject.org/pipermail/tor-relays/2020-March/018306.html
I don't think the bug log should be there.Tor: 0.4.4.x-finalGeorge KadianakisGeorge Kadianakishttps://gitlab.torproject.org/legacy/trac/-/issues/33765Windows Tor Browser 9.0.7 Hamburger Menu Differs from OSX/Linux Version2020-06-16T01:12:12ZNicolei OcaƱaWindows Tor Browser 9.0.7 Hamburger Menu Differs from OSX/Linux VersionAfter pressing the hamburger menu for the Windows version of Tor Browser 9.0.7, there is an "Options" option. This differs from the OSX/Linux versions where the option is identified as "Preferences."After pressing the hamburger menu for the Windows version of Tor Browser 9.0.7, there is an "Options" option. This differs from the OSX/Linux versions where the option is identified as "Preferences."https://gitlab.torproject.org/legacy/trac/-/issues/33929Tor relay appears offline in Metrics after some times2020-06-13T15:53:12ZTracTor relay appears offline in Metrics after some timesSince at least December 20, my relay appears offline in Metrics after few hours to few days (typically between 3h to 3d). In nyx, all flags disappears. After restarting the service, flags are coming back after few hours and the relay app...Since at least December 20, my relay appears offline in Metrics after few hours to few days (typically between 3h to 3d). In nyx, all flags disappears. After restarting the service, flags are coming back after few hours and the relay appears online again. There is nothing in the log.
My fingerprint:
33D88F331408141F2A2CC563239E54E48F7A211B
Notice that this happens to at least another person, its fingerprint
DAA806E9529D77EF94685FC0E513386EF65B83F8
**Trac**:
**Username**: clementhttps://gitlab.torproject.org/legacy/trac/-/issues/34038Video but no sound in TOR, Knoppix OS2020-06-16T01:12:49ZTracVideo but no sound in TOR, Knoppix OSI'm running an unaltered Knoppix OS from a USB, on a Dell Latitude E6500 laptop: 2 core, Intel 45 chipset, 64bit capable but only running 32 bit; 512 & 8 GB memory capable but 2 GB memory installed.
"About" in the browser says this is...I'm running an unaltered Knoppix OS from a USB, on a Dell Latitude E6500 laptop: 2 core, Intel 45 chipset, 64bit capable but only running 32 bit; 512 & 8 GB memory capable but 2 GB memory installed.
"About" in the browser says this is Tor 9.0.9, up to date,Firefox 68.7.0esr) (32-bit) up to date.
While in Windows 7 Ultimate (32 bit), sound & video work fine locally & on web in both Firefox and TOR. In Knoppix, both work locally & in Firefox. But in Knoppix in TOR, I can play video but THERE's NO SOUND.
I'm illiterate in unix/debian commands. This is all new to me. Can someone guide me in plainspeak through trying some fixes in Knoppix?
I'm coming up empty on the internet. I would very much appreciate any help. Thank you - AntiDiluv
**Trac**:
**Username**: AntiDiluvhttps://gitlab.torproject.org/legacy/trac/-/issues/34039Video but no sound in TOR, Knoppix OS2020-06-16T01:12:50ZTracVideo but no sound in TOR, Knoppix OSI'm running an unaltered Knoppix OS from a USB, on a Dell Latitude E6500 laptop: 2 core, Intel 45 chipset, 64bit capable but only running 32 bit; 512 & 8 GB memory capable but 2 GB memory installed.
"About" in the browser says this is...I'm running an unaltered Knoppix OS from a USB, on a Dell Latitude E6500 laptop: 2 core, Intel 45 chipset, 64bit capable but only running 32 bit; 512 & 8 GB memory capable but 2 GB memory installed.
"About" in the browser says this is Tor 9.0.9, up to date,
Firefox 68.7.0esr) (32-bit) up to date.
While in Windows 7 Ultimate (32 bit), sound & video work fine locally & on web in both Firefox and TOR. In Knoppix, both work locally & in Firefox. But in Knoppix in TOR, I can play video but THERE's NO SOUND.
I'm illiterate in unix/debian commands. This is all new to me. Can someone guide me in plainspeak through trying some fixes in Knoppix?
I'm coming up empty on the internet. I would very much appreciate any help. Thank you.
**Trac**:
**Username**: AntiDiluvhttps://gitlab.torproject.org/legacy/trac/-/issues/34040Video but no sound in TOR, Knoppix OS2020-06-13T15:53:17ZTracVideo but no sound in TOR, Knoppix OSI'm running an unaltered Knoppix OS from a USB, on a Dell Latitude E6500 laptop: 2 core, Intel 45 chipset, 64bit capable but only running 32 bit; 512 & 8 GB memory capable but 2 GB memory installed.
"About" in the browser says this is...I'm running an unaltered Knoppix OS from a USB, on a Dell Latitude E6500 laptop: 2 core, Intel 45 chipset, 64bit capable but only running 32 bit; 512 & 8 GB memory capable but 2 GB memory installed.
"About" in the browser says this is Tor 9.0.9, up to date,Firefox 68.7.0esr) (32-bit) up to date.
While in Windows 7 Ultimate (32 bit), sound & video work fine locally & on web in both Firefox and TOR. In Knoppix, both work locally & in Firefox. But in Knoppix in TOR, I can play video but THERE's NO SOUND.
I'm illiterate in unix/debian commands. This is all new to me. Can someone guide me in plainspeak through trying some fixes in Knoppix?
I'm coming up empty on the internet. I would very much appreciate any help. Thank you.
**Trac**:
**Username**: AntiDiluvhttps://gitlab.torproject.org/legacy/trac/-/issues/34199torsocks irssi weird bug2020-06-13T16:10:11ZTractorsocks irssi weird bugDepending on the arguments to torsocks the output varies even though it shouldn't
case-1: torsocks irssi
`/connect oftc` gives following error
Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system call]
case 2: tor...Depending on the arguments to torsocks the output varies even though it shouldn't
case-1: torsocks irssi
`/connect oftc` gives following error
Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system call]
case 2: torsocks -d irssi
`/connect oftc` works as expected
I don't think there should be difference in output just because logging is enabled. This just might be the "torsocks uncertainty principle". I think we are onto something. Below I've attached the log dumped on the terminal.
1589343629 DEBUG torsocks[22051]: Logging subsytem initialized. Level 5, file (null), time 1 (in init_logging() at torsocks.c:303)
1589343629 DEBUG torsocks[22051]: Config file not provided by TORSOCKS_CONF_FILE. Using default /etc/torsocks.conf (in config_file_read() at config-file.c:543)
1589343629 DEBUG torsocks[22051]: Config file setting tor address to 127.0.0.1 (in conf_file_set_tor_address() at config-file.c:298)
1589343629 DEBUG torsocks[22051]: Config file setting tor port to 9050 (in conf_file_set_tor_port() at config-file.c:254)
1589343629 DEBUG torsocks[22051]: [config] Onion address range set to 127.42.42.0/24 (in set_onion_info() at config-file.c:108)
1589343629 DEBUG torsocks[22051]: Config file /etc/torsocks.conf opened and parsed. (in config_file_read() at config-file.c:572)
1589343629 DEBUG torsocks[22051]: [fclose] Close caught for fd 3 (in tsocks_fclose() at fclose.c:45)
1589343629 DEBUG torsocks[22051]: [onion] Pool init with subnet 127.42.42.0 and mask 24 (in onion_pool_init() at onion.c:104)
1589343629 DEBUG torsocks[22051]: [onion] Pool initialized with base 0, max_pos 255 and size 8 (in onion_pool_init() at onion.c:132)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
**Trac**:
**Username**: crab