Bugs related to Tor logs at the [sys-whonix] tor-control-panel

User Support
1

Hello community! Thank you all in advance who take your time to read, comment & trying to be helpful to me & all the community members, I do appreciate it a lot, THANK YOU :slight_smile:

This bug popin up each 10-40 min while I am online, it also decrease my onion circuits till I have zero circuits. To get back online I do “Restart Tor” (at the sys-whonix control panel) or “Restart sdwdate”, sometimes even both, restart tor & sdwdate.
(why do I restart sdwdate? -because it gives me a new onion-circuits similar to “New Identity” button. “New Identity” button lagging so so bad! it is much easier to restart sdwdate than wait & hope for a few minutes or more till OS will give me new identity credentials)

Questions:

  1. How to fix this issue or when Developers will fix this problem?
  2. How dangerous this issue?
    How this issue/bugs effect my privacy & anonymity?
  3. Something else should I be caution about?

[sys-whonix] tor-control-panel
Bugs related to Tor logs:

**[warn] tor_bug_occurred_(): Bug: ../src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.15 )**
**[warn] Bug: Tor 0.4.8.15: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ../src/core/or/conflux_util.h:31. Stack trace: (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(log_backtrace_impl+0x57) [0x64d84bf111d7] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_bug_occurred_+0x169) [0x64d84bf1c139] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(circuit_describe_status_for_controller+0x483) [0x64d84bfe2b93] (on Tor 0.4.8.15 )*
**[warn] Bug: /usr/bin/tor(control_event_circuit_status+0xbd) [0x64d84bfded0d] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(circuit_close_all_marked+0x17d) [0x64d84bf8a43d] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(+0x70349) [0x64d84be96349] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x21482) [0x7f009f549482] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x49f) [0x7f009f549c1f] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(do_main_loop+0xf1) [0x64d84be976c1] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_run_main+0x1e5) [0x64d84be92ff5] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_main+0x59) [0x64d84be8f329] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(main+0x19) [0x64d84be8eee9] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7f009ec4624a] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f009ec46305] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(_start+0x21) [0x64d84be8ef31] (on Tor 0.4.8.15 )**
**[warn] tor_bug_occurred_(): Bug: ../src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.15 )**
**[warn] Bug: Tor 0.4.8.15: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ../src/core/or/conflux_util.h:31. Stack trace: (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(log_backtrace_impl+0x57) [0x64d84bf111d7] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_bug_occurred_+0x169) [0x64d84bf1c139] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(circuit_describe_status_for_controller+0x483) [0x64d84bfe2b93] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(control_event_circuit_status+0xbd) [0x64d84bfded0d] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(circuit_close_all_marked+0x17d) [0x64d84bf8a43d] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(+0x70349) [0x64d84be96349] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x21482) [0x7f009f549482] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x49f) [0x7f009f549c1f] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(do_main_loop+0xf1) [0x64d84be976c1] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_run_main+0x1e5) [0x64d84be92ff5] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_main+0x59) [0x64d84be8f329] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(main+0x19) [0x64d84be8eee9] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7f009ec4624a] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f009ec46305] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(_start+0x21) [0x64d84be8ef31] (on Tor 0.4.8.15 )**
**[warn] tor_bug_occurred_(): Bug: ../src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.15 )**
**[warn] Bug: Tor 0.4.8.15: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ../src/core/or/conflux_util.h:31. Stack trace: (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(log_backtrace_impl+0x57) [0x64d84bf111d7] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_bug_occurred_+0x169) [0x64d84bf1c139] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(circuit_describe_status_for_controller+0x483) [0x64d84bfe2b93] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(control_event_circuit_status+0xbd) [0x64d84bfded0d] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(circuit_close_all_marked+0x17d) [0x64d84bf8a43d] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(+0x70349) [0x64d84be96349] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x21482) [0x7f009f549482] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x49f) [0x7f009f549c1f] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(do_main_loop+0xf1) [0x64d84be976c1] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_run_main+0x1e5) [0x64d84be92ff5] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(tor_main+0x59) [0x64d84be8f329] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(main+0x19) [0x64d84be8eee9] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7f009ec4624a] (on Tor 0.4.8.15 )**
**[warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f009ec46305] (on Tor 0.4.8.15 )**
**[warn] Bug: /usr/bin/tor(_start+0x21) [0x64d84be8ef31] (on Tor 0.4.8.15 )**

ps. original text was all highlighted with yellow color, if it’s matter.

1 Like
2

Unrelated to Qubes OS or Whonix OS. Tor upstream bug
You can fix it if add to torrc file this line

ConfluxEnabled 0

As far as I can tell from the Tor documentation, this “patch” does not have any impact on anonymity, security, etc. It just slightly reduces the connection speed.

This does not affect your security (except that it sometimes causes your network to crash).

Only Tor developers can fix this bug cleanly (without disable conflux). The corresponding issue has been sitting idle for about a year now.

I got same error on Debian as main os (not VM).

1 Like
3

What “ConfluxEnabled 0” does to a system?

How it’s not affecting my anonymity if I need to restart Tor [sys-whonix] and sdwdate constantly? (1-4 times in an hour)

also I’m not using Tor-browser now, because I afraid this Bug definitely compromised my onion circuits and after all expose my IP address.

also I don’t get it, why nobody except me talking about this bug, if it’s Tor related Bug everyone had it now, in last few weeks, and I’m sure here we have really “Big folks” who need to be caution about it

idk to who can I address this, but moderators please pin this post/move to right categories/ tag it or do something to get involve more people to this, I think it is really important topic and yes it is related to qubes even it is on tor team side.

Thank you all!

@solene @deeplow @adw @Sven @unman @system

1 Like
4

You are greatly overestimating the seriousness of this bug in the context of anonymity and privacy. And it did not appear a few weeks ago. This bug has been present since the November 2023 version of Tor. If you consider it so serious, it would be logical to send your demands for its urgent fix directly to Tor, since the Tor developers have shown no interest in solving this problem and do not consider it. And it is unlikely that anything will change from causing panic in the Qubes OS community. I wrote how you can trivially avoid this bug without compromising anonymity and privacy. I doubt that Qubes OS developers should solve bugs that affect Tor on all platforms

1 Like
5

As mentioned, this is a Tor-specific issue. Please report to Tor or discuss on their forum. The Qubes forum is for Qubes topics.

Closing.

1 Like