WalletWasabi: Cannot start Wasabi on my new Linux laptop

Don’t have such problem with my other Linux machines, not sure right now what is exact cause of the problem. Tried with master and v1.1.5 built from sources and with v1.1.3, v1.1.4 and v1.1.5 pre-built releases.

With master built from sources, it kinda starts, but GUI does not appear and I end up just with some dotnet processes running. (replaced some of my true paths and username with XXX in output)

$ DOTNET_SKIP_FIRST_TIME_EXPERIENCE=true dotnet run
2019-06-05 01:11:34 INFO 3e5edc46-58bb-4359-83bc-0ce599b632a7: Wasabi GUI is starting...
2019-06-05 01:11:36 INFO Config: Config file did not exist. Created at path: `XXX/.walletwasabi/client/Config.json`.
2019-06-05 01:11:37 INFO Config: Config is successfully initialized.
2019-06-05 01:11:37 INFO: Using HOME environment variable for initializing application data at `XXX/.walletwasabi/client`.
2019-06-05 01:11:37 INFO HwiProcessManager: HWI instance NOT found at XXX/.walletwasabi/client/hwi/hwi. Attempting to acquire it...
2019-06-05 01:11:37 INFO HwiProcessManager: Extracted XXX/git/WalletWasabi/WalletWasabi.Gui/bin/Debug/netcoreapp2.2/Hwi/Software/hwi-linux64.zip to XXX/.walletwasabi/client/hwi.
2019-06-05 01:11:37 INFO HwiProcessManager: Shell command executed: chmod -R 750 XXX/.walletwasabi/client/hwi.
2019-06-05 01:11:37 INFO AddressManager: AddressManager did not exist at `XXX/.walletwasabi/client/AddressManager/AddressManagerMain.dat`. Initializing new one.
2019-06-05 01:11:37 INFO TorProcessManager: Starting Tor monitor...
2019-06-05 01:11:37 INFO TorProcessManager: TorProcessManager is initialized.
2019-06-05 01:11:37 INFO Config: Config file did not exist. Created at path: `XXX/.walletwasabi/client/UiConfig.json`.
2019-06-05 01:11:37 INFO TorProcessManager: Tor is already running.
2019-06-05 01:11:37 INFO: Start connecting to nodes...
2019-06-05 01:11:37 INFO: Start synchronizing filters...
2019-06-05 01:11:37 INFO UiConfig: UiConfig is successfully initialized.
$ ps afux|grep dotnet
XXX    15742  0.0  0.0  16820   992 pts/1    S+   01:12   0:00      \_ grep --colour=auto dotnet
XXX    15589  3.6  0.9 3417812 76956 pts/1   SLl  01:11   0:01 /opt/dotnet_core/dotnet /opt/dotnet_core/sdk/2.2.103/MSBuild.dll /opt/dotnet_core/sdk/2.2.103/MSBuild.dll /nologo /nodemode:1 /nodeReuse:true
XXX    15605  4.4  1.0 3811028 82548 pts/1   SLl  01:11   0:01 /opt/dotnet_core/dotnet /opt/dotnet_core/sdk/2.2.103/MSBuild.dll /opt/dotnet_core/sdk/2.2.103/MSBuild.dll /nologo /nodemode:1 /nodeReuse:true
XXX    15636  2.8  0.9 3409340 72804 pts/1   SLl  01:11   0:00 /opt/dotnet_core/dotnet /opt/dotnet_core/sdk/2.2.103/MSBuild.dll /opt/dotnet_core/sdk/2.2.103/MSBuild.dll /nologo /nodemode:1 /nodeReuse:true

With pre-built releases, it ends up with a segmentation fault:

$ ./wassabee 
2019-06-05 01:15:21 INFO 215dfb1d-7296-4b7e-bd53-59d7515d4752: Wasabi GUI is starting...
2019-06-05 01:15:25 INFO Config: Config is successfully initialized.
2019-06-05 01:15:25 INFO: Using HOME environment variable for initializing application data at `XXX/.walletwasabi/client`.
2019-06-05 01:15:25 INFO HwiProcessManager: Updating HWI...
2019-06-05 01:15:25 INFO HwiProcessManager: Extracted XXX/Lejupielādes/WasabiLinux-1.1.5/Hwi/Software/hwi-linux64.zip to XXX/.walletwasabi/client/hwi.
2019-06-05 01:15:25 INFO HwiProcessManager: Shell command executed: chmod -R 750 XXX/.walletwasabi/client/hwi.
2019-06-05 01:15:25 INFO TorProcessManager: Starting Tor monitor...
2019-06-05 01:15:25 INFO TorProcessManager: TorProcessManager is initialized.
2019-06-05 01:15:25 INFO AddressManager: AddressManager did not exist at `XXX/.walletwasabi/client/AddressManager/AddressManagerMain.dat`. Initializing new one.
2019-06-05 01:15:25 INFO UiConfig: UiConfig is successfully initialized.
2019-06-05 01:15:25 INFO TorProcessManager: Tor is already running.
2019-06-05 01:15:26 INFO: Start connecting to nodes...
2019-06-05 01:15:26 INFO: Start synchronizing filters...
Segmentation fault

Not so sure how to properly debug .Net programs under Linux, gdb does not give much useful info, except that GUI appears in a taskbar before segfault. image

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 26 (12 by maintainers)

Commits related to this issue

Most upvoted comments

Current master with #1624 merged solves this issue for me.

@kristapsk think I have an idea what is happening here. Need to investigate how I would fix. Basically we need to detect when system is using LLVMpipe, and fallback to software rendering in this case.

I will post an update once we have something tested.