Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error creating client: failed to unlock correct collection '/org/freedesktop/secrets/aliases/default' #25

Open
hwebb opened this issue Jun 2, 2021 · 1 comment

Comments

@hwebb
Copy link

hwebb commented Jun 2, 2021

Error when trying to connect via Linux SSH!

@prannonpendragas
Copy link

I had similar problems, but I found a workaround after lengthy and mostly fruitless research here: https://unix.stackexchange.com/a/548005

My WSL environment is ubuntu 22.04.

When you launch your WSL, run these commands:

sudo systemctl restart [email protected] # to make sure that your user has a DBUS
sudo apt-get update
sudo apt-get install gnome-keyring libsecret-tools dbus-x11 # to install needed software
sudo killall gnome-keyring-daemon # to kill any running keyring daemons; most likely there will be none running since I think that WSL2 has the keyring daemon disabled by default
eval "$(printf '\n' | gnome-keyring-daemon --unlock)" # trick the system into thinking you've logged in, creating the needed keyring
eval "$(printf '\n' | /usr/bin/gnome-keyring-daemon --start)" # start up the keyring, making it available for xoauth

You can test to see if all this worked by running commands such as this:

secret-tool lookup foo bar
printf "aPassword" | secret-tool store --label="test" foo bar
secret-tool lookup foo bar

If you get the aPassword string back after running these, then the keyring is set up and you are probably past this problem. Good luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants