Walletwasabi: Wasabi 1.1.9.3 does not start on Tails 4.1

Created on 9 Dec 2019 · 20Comments · Source: zkSNACKs/WalletWasabi

General Description

Wasabi 1.1.9.3 does not start on Tails 4.1, hangs with a completely gray screen on an empty .wasabiwallet config directory and has to be killed. I believe it has to do with local Tor detection on Tails 4.1 (latest).

How To Reproduce?

Use Tails 4.1.
Open wassabee with an empty config directory.
Wasabi hangs with a gray screen with an obscure upward arrow at the bottom, which is not clickable/draggable.

Operating System

Tails 4.1.

Logs

2019-12-09 20:27:35 INFO    Program (44)    Wasabi GUI started (3574218d-ea49-XXXX-XXXX-XXXXXXXXXXX).
2019-12-09 20:27:36 INFO    ConfigBase (63) Config file did not exist. Created at path: `/home/amnesia/.walletwasabi/client/Config.json`.
2019-12-09 20:27:36 INFO    ConfigBase (63) UiConfig file did not exist. Created at path: `/home/amnesia/.walletwasabi/client/UiConfig.json`.
2019-12-09 20:27:37 INFO    Global (158)    Config is successfully initialized.
2019-12-09 20:27:37 INFO    TransactionStore (28)   MempoolStore.InitializeAsync finished in 21 milliseconds.
2019-12-09 20:27:37 INFO    TransactionStore (28)   ConfirmedStore.InitializeAsync finished in 11 milliseconds.
2019-12-09 20:27:37 INFO    AllTransactionStore (27)    InitializeAsync finished in 36 milliseconds.
2019-12-09 20:27:37 INFO    Global (391)    AddressManager did not exist at `/home/amnesia/.walletwasabi/client/AddressManager/AddressManagerMain.dat`. Initializing new one.
2019-12-09 20:27:37 INFO    TorProcessManager (249) Starting Tor monitor...
2019-12-09 20:27:37 INFO    Global (220)    TorProcessManager is initialized.
2019-12-09 20:27:37 INFO    MainWindow.xaml (74)    UiConfig is successfully initialized.
2019-12-09 20:27:37 INFO    TorProcessManager (66)  Tor is already running.

Wasabi Version

Wasabi 1.1.9.3

debug stale

Source

mikispag

Most helpful comment

Just built from master, modifying logging level to debug for a release build. Will update.

mikispag on 10 Dec 2019

👍2

All 20 comments

Works for me. Cannot reproduce

RiccardoMasutti on 9 Dec 2019

I have uploaded my logs. After that, Wasabi hangs indefinitely and I have to kill it. ^C does not work.

mikispag on 9 Dec 2019

It doesn't seem to be related to Tor imo.

Q: what do you mean by empty config directory? It is the ~/.config directory or the ~/.walletwasabi directory?
Q: did wasabi work for you in previous versions?
Q: are you running it from code?

Any additional info would be really useful. Given you are a Tails users by sure you know better than me where to take a look for that.

lontivero on 9 Dec 2019

It doesn't seem to be related to Tor imo.

Running it under strace -p PID -f it looks like it is caught in a futex wait queue.

I see many of these:

futex(0x5587f00, FUTEX_WAIT_PRIVATE, 2, {0, 1925684}) = -1 ETIMEDOUT (Connection timed out)

Q: what do you mean by empty config directory? It is the ~/.config directory or the ~/.walletwasabi directory?

Empty ~/.walletwasabi directory, vanilla Tails 4.1.

Q: did wasabi work for you in previous versions?

Yes. It worked with 1.1.9.1.

Q: are you running it from code?

No, I am running the 1.1.9.3 release from deb.

Any additional info would be really useful. Given you are a Tails users by sure you know better than me where to take a look for that.

Would love to help debugging, but I have posted Logs.txt. Tor Logs are not there.

mikispag on 10 Dec 2019

Thank you for the report. Can you confirm that it is working with 1.1.9.2 (Latest release) with Tails 4.1?

molnard on 10 Dec 2019

Thank you for the report. Can you confirm that it is working with 1.1.9.2 (Latest release) with Tails 4.1?

It works for me

RiccardoMasutti on 10 Dec 2019

1.1.9.2. loads correctly on the same Tails 4.1.

Is there a way to have more detailed debug logs, maybe a hidden command line flag? In other words, how do you debug "hanging and nothing visible happens for hours" cases?

mikispag on 10 Dec 2019

There is not way to have a more detailed logs using the packaged version. If you run it from code then you can change the log level to debug here https://github.com/zkSNACKs/WalletWasabi/blob/0170b2728917349834a5cb66cbb28ba24bd44c36/WalletWasabi/Logging/Logger.cs#L62

What I understand from you last comment (and for the strace) is that wasabi starts but enters probably in a deadlock. The question is why this happens on Tails only.

lontivero on 10 Dec 2019

This is an edge-case might be an issue. Anyway, you provide a detailed description, so I will give 2 points for reporting this.

molnard on 10 Dec 2019

Just built from master, modifying logging level to debug for a release build. Will update.

mikispag on 10 Dec 2019

👍2

So, pretty hard to debug this.

Apparently, this was briefly fixed by installing libgdiplus_6.0.4.-0xamarin1+debian10b1_amd64.deb from https://download.mono-project.com/repo/debian/pool/main/libg/libgdiplus/libgdiplus_6.0.4-0xamarin1+debian10b1_amd64.deb. I saw the GUI pop up briefly, and then it segfaults without any helpful log entries. I have tried removing the .walletwasabi directory completely and rebooting the Tails system many times.

mikispag on 11 Dec 2019

@mikispag do you have .NET Core 3.1 installed? That got updated in master, after RC1 I believe.

MaxHillebrand on 11 Dec 2019

This might be related #2836

Apparently workaround is downgrade libglvnd-1.3.0-1 to libglvnd-1.2.0.5

MaxHillebrand on 11 Dec 2019

Yes, I do have dotnet-sdk-3.1 installed from Microsoft deb repo for Debian 10.
I did not have libglvnd-dev nor libglvnd0 installed in Tails.
I installed both, at version 1.1.0-1, which is the same as debian buster.

Problem persists. I just see a gray window with an obscure upward arrow at the bottom, which is not clickable/draggable. Same behavior on HEAD, but the "Click and Drag upwards to unlock." text is there instead of the arrow. I tried every time with a clean .walletwasabi directory and clean Tails 4.1.

mikispag on 11 Dec 2019

😕1

Can you try reproducing on a vanilla Tails 4.1 installing dotnet-sdk-3.1 only?

mikispag on 11 Dec 2019

Still does not work at 809bceee39ae71279176cc563e937fa5bb7910d1. I confirm that 1.1.9.2 works with the same setup.

Why does it start in "screen lock" mode with an empty .walletwasabi and never goes out of it?

mikispag on 13 Dec 2019

Can u try with this?
https://github.com/molnard/WalletWasabi/releases/tag/v1.1.10rc2

molnard on 13 Dec 2019

Thanks, tried. Click and drag upwards to unlock. Nothing happens. Nothing is draggable. When I try to close the window with the top-right X button, the top-right icons disappear. CTRL+C does not exit and I have to manually kill the process. It might have to do with some Tails-specific settings related to window sizes (to prevent leaking of window sizes)?

Did you try with a clean Tails 4.1? I believe it is easy to reproduce.

mikispag on 13 Dec 2019

@mikispag
Do you still have this issue?
Can you try with a newer version? or with the v1.1.12rc2 https://github.com/molnard/WalletWasabi/releases/tag/v1.1.12rc2

yahiheb on 27 Jul 2020

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.