WSL2 - Unknown or unsupported transport

[rjackson-dev-ops]

Describe the bug
Running this in WSL 2, I see this error trying to save creds:

(leapp:6480): libappindicator-WARNING **: 05:03:44.798: Unable to get the session bus: Unknown or unsupported transport “disabled” for address “disabled:”

I have been using aws-vault with "pass" as my backend. I suspect Leapp is using gnome perhaps and maybe gnone keyring has to be started before leapp.

I'm running this code right now to make it work before I launch leapp.

Unknown or unsupported transport

sh -e /etc/init.d/xvfb start; sleep 3;
export NO_AT_BRIDGE=1; # Don't use dbus accessibility bridge
eval $(dbus-launch --sh-syntax);
eval $(echo -n "" | /usr/bin/gnome-keyring-daemon --login);
eval $(/usr/bin/gnome-keyring-daemon --components=secrets --start);
/usr/bin/python -c "import gnomekeyring;gnomekeyring.create_sync('login', '');";

Leapp Version
Latest - installed yesterday

To Reproduce
Steps to reproduce the behavior:

1. Install Leapp on Ubuntu running in WSL
2. Try to save creds

Expected behavior
Save creds with not isues.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• OS Version [e.g. 22]
• Leapp Version [e.g. 0.2.5]

Additional context
Add any other context about the problem here.

[pethron]

Thanks for reporting this issue, I agree that seems an issue with keytar and the start of the gnome-keyring.

Currently, we are switching the core logic to an engine written in go that will use this library https://github.com/zalando/go-keyring. It currently has an issue open related to this problem but they found a workaround zalando/go-keyring#48. Due to the logic migration, we can't afford to patch up keytar (but feel free to make a pull request if you find a working solution).

It could be better to use some help in testing the go engine on WSL.

[raajpackt]

Can it be explained how to install Leapp in wsl?

[ghost]

Can it be explained how to install Leapp in wsl?

One way to do it:

1. Install Leapp in Windows
2. Open WSL
3. In WSL backup your ~/.aws and ~/.azure
4. In WSL create symlink from /mnt/c/Users/<username>/.aws to ~/.aws
5. In WSL create symlink from /mnt/c/Users/<username>/.azure to ~/.azure

Example:

# It is ok, if the command returns cp: cannot stat '.aws': No such file or directory
cp -av ~/.aws ~/.aws.bak
# It is ok, if the command returns cp: cannot stat '.azure': No such file or directory
cp -av ~/.azure ~/.azure.bak

ln -s /mnt/c/Users/<username>/.aws ~/.aws
ln -s /mnt/c/Users/<username>/.azure ~/.azure

Then WSL will follow chosen session in Windows Leapp. One caveat is that Leapp CLI doesn't work in WSL.

[andreacavagna01]

Can we now add this snippet to the documentation and close the issue?

[mtb-xt]

Symlinking a windows folder to WSL directory seems like a hack to me.
Ideally, either make Leapp GUI work from within the WSL (it doesn't at the moment, and other electron apps do work) - or make it possible to use the CLI from WSL to windows Gui app.