PR | Description | Win | Mac | Lin
-- | -- | -- | -- | --
17 | Use the UI and check memory usage if increasing endlessly - memory leak. | ✗ | |  ✗
When I click Open>Tor Log File, No file / folder is opened (tried both on Debian and TAILS)

Same here.. Upon investigation, there isn't any tor log file being created at all.. So the menu is trying to open up a non-existent file.
Seems to happen only when the system Tor daemon is used instead of wasabi's built-in ones, or if the daemon is already running. I guess the menu could be disabled in that situation but that's a new feature and shouldn't be included in this release.
Same here.. Upon investigation, there isn't any tor log file being created at all.. So the menu is trying to open up a non-existent file.
Seems to happen only when the system Tor daemon is used instead of wasabi's built-in ones, or if the daemon is already running. I guess the menu could be disabled in that situation but that's a new feature and shouldn't be included in this release.
@davterra said:
I am able to open 'Open > Tor Log File' using Ubuntu 19.04
yeah, the codepath for the menu is fine, it's just that the backend isnt creating the TorLog file for some reason.. Did he install Tor and enabled it on startup or not?
that's a good catch @RiccardoMasutti ! 2 points
@MaxHillebrand Are you able to reproduce the issue with Qubes/Debian/Fedora? I am not able to reproduce it with Ubuntu 19.04
It happens when someone doesn't uses Wasabi's built in Tor but uses external Tor instead.
Most helpful comment
It happens when someone doesn't uses Wasabi's built in Tor but uses external Tor instead.