Onion Circuits window is not responding
With network connection disabled and starting Onion Circuits at the top of the window it says:
You are not connected to Tor yet...
This freezes the window (not responding) so i can't move it or anything.
With network connection enabled the window is working fine.
#1 Updated by mercedes508 about 1 year ago
- Status changed from New to Confirmed
- Assignee set to alant
- Priority changed from Normal to Low
- Target version set to Tails_3.13
OK, so yes, when network is disabled form greeter, when opening onion circuits, it doesn't freeze the system, but the onion circuits window is not actionable (can't close/resize it by clicking on buttons).
Which is really low prio because anyway if you don't use network, you don't have to use onion circuits at all.
#3 Updated by tailshark about 1 year ago
There are a handful of weird things with onion circuits and I'm not sure if they're an upstream problem or not.
- If you disconnect and reconnect repeatedly with the onion circuits window open it can stop reporting anything at all. That is: You'll get a blank/empty circuit window while you're actually connected to Tor. (problem state manifests intermittently)
- If you disconnect and reconnect repeatedly with the onion circuits window open the circuits can display but you can't click or scroll on the circuits themselves. It'll always auto-scroll you to the top circuit when you try to click or interact with entries in the window. (problem state manifests intermittently)
- In some cases Onion Circuits will just outright freeze when disconnect/reconnecting.
The fix for all of the above has been to close onion circuits (perhaps forcibly) and turn it back on. I'm sort of getting accustomed to force-closing onion circuits and opening it again. I sometimes use Tails on a finnicky LAN environment with a proxy exit so I may be noticing this more than most.
On that note there is a corollary issue that is more difficult to demonstrate. The "onion-grater" service can begin consuming high CPU for no apparent reason after long periods of uptime and several disconnects/reconnects. Simply restarting the service "service onion-grater restart" seems to fix it. I thought I would bring this up since onion-grater seems to provide a data feed for onion circuits. It's possible there is some kind of race condition or connection handling problem between the two.
I'm not expecting anyone to leap to try and fix this. I haven't bothered myself since it's a menial chore to restart the window/service. But I thought having more information here on the record is better than less.