Walletwasabi: CRITICAL Program: System.Exception: XOpenDisplay failed

[nidkil]

General Description

I have installed Wasabi Wallet on Manjaro 18.0.4 and I'm getting the following error when starting ./wassabee:

[nidkil@nidkil-manjaro WasabiLinux-1.1.6]$ ./wassabee 
2019-08-09 02:49:27 INFO 1c18b5fb-e097-4621-b688-f9a37c89228a: Wasabi GUI is starting...
2019-08-09 02:49:27 CRITICAL Program: System.Exception: XOpenDisplay failed
   at Avalonia.X11.AvaloniaX11Platform.Initialize(X11PlatformOptions options)
   at Avalonia.Controls.AppBuilderBase`1.Setup()
   at Avalonia.Controls.AppBuilderBase`1.Start[TMainWindow](Func`1 dataContextProvider)
   at WalletWasabi.Gui.Program.Main(String[] args)
2019-08-09 02:49:27 INFO 1c18b5fb-e097-4621-b688-f9a37c89228a: Wasabi GUI stopped gracefully.

Unhandled Exception: System.Exception: XOpenDisplay failed
   at Avalonia.X11.AvaloniaX11Platform.Initialize(X11PlatformOptions options)
   at Avalonia.Controls.AppBuilderBase`1.Setup()
   at Avalonia.Controls.AppBuilderBase`1.Start[TMainWindow](Func`1 dataContextProvider)
   at WalletWasabi.Gui.Program.Main(String[] args)
   at WalletWasabi.Gui.Program.Main(String[] args)
   at WalletWasabi.Gui.Program.<Main>(String[] args)
Aborted (core dumped)

How To Reproduce?

# Download
cd ~/Downloads
VERSION=1.1.6
NAME=WasabiLinux-${VERSION}
wget https://github.com/zkSNACKs/WalletWasabi/releases/download/v${VERSION}/${NAME}.tar.gz
wget https://github.com/zkSNACKs/WalletWasabi/releases/download/v${VERSION}/${NAME}.tar.gz.asc
wget https://raw.githubusercontent.com/zkSNACKs/WalletWasabi/master/PGP.txt

# Verify
gpg --import PGP.txt
gpg --verify ${NAME}.tar.gz.asc ${NAME}.tar.gz

# Install
tar -pxzf ${NAME}.tar.gz
mv ${NAME} ~/.

# Cleanup
rm PGP.txt Wasabi*

# Run
cd ~/${NAME}
./wassabee

Screenshots

N/A

Operating System

Please consider your privacy, before completing this section.
Example: Manjaro 18.0.4

Logs

N/A

Wasabi Version

See How To Reproduce? section.

[nidkil]

Hi,

This seems to be an issue with the terminal I was using. After executing wassabee in a different terminal it works.

Sorry for the confusion.

[benthecarman]

Glad you were able to fix it!

[MaxHillebrand]

Thanks for opening the issue here again :)
good that it's working now!
Could you please share what terminal did not work, and which one is fine?
Maybe this is still a bug in Wasabi...?

[nidkil]

It is not a bug in Wasabi, but a fluke :-)

I updated the groups of my account and used the following command exec su -l $USER to reload the groups without logging out and in again. It spawns a new shell in the same terminal. In the new shell the DISPLAY variable is not set, which causes the error. The environment variable DISPLAY tells GUI programs how to communicate with the GUI. If I manually set export DISPLAY=":0.0" it works.

So no worries, Wasabi works fine.

[nidkil]

If you guys are interested I setup a bash script to automate the installation and setup of the Other Version of Wasabi Wallet. You can find it here.

[nopara73]

@nidkil That's a great script! I was thinking if we should move to more of a terminal-based installation on Linuxes, too. We don't do this currently, but will reconsider later on.

[lontivero]

@nidkil I like your script. I think it it how it should be installed in many linux distros. In fact I have my own script to do exactly the same but the yours one looks much better.

IMO wasabi should be installed as follow:

curl https://raw.githubusercontent.com/nidkil/wasabi-other-linux-setup/master/setup.sh | sh

[nidkil]

@lontivero thx for the tip. I changed the usage to:

bash <(curl -sS https://raw.githubusercontent.com/nidkil/wasabi-other-linux-setup/master/setup.sh)

The way you suggested does not work for an interactive shell.

[nidkil]

@nopara73 Is it an idea to add a comment in the documentation, so that users now that the script is available?

[nopara73]

@nidkil for security reasons we cannot risk pointing to your script, but we can fork it and can point to that. I think the current way is sufficient, but if @MaxHillebrand or @lontivero would like to review your script, I wouldn't be against it.