microsoft/live-share

[VS Code][ArchLinux] Arch Linux secret_password_clear_sync() failed with error code 2: The name org.freedesktop.secrets was not provided by any .service files

Closed this issue · 12 comments

malteA commented

Error:

secret_password_clear_sync() failed with error code 2: The name org.freedesktop.secrets was not provided by any .service files

Steps to Reproduce:

  1. Install 'visual-studio-code-bin' from AUR
  2. Install Live Share
  3. Sign into GitHub Account and copy provided Code
  4. Wait 10sec and the error Message appears
Version Data
extensionName VSLS
extensionVersion 0.2.404
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.22.2
platformName Linux
platformVersion 4.15.13-1-ARCH
Chuxel commented

@malteA This is potentially a dupe of #213. What desktop environment are you using? Also are you on vanilla arch or a distro like Manjaro?

Also, can you verify you all dependencies installed including gnome-keychain? The error indicates you may not.

Chuxel commented

@malteA Checking out Arch, you likely don't have gnome-keyring and libsecret installed.

Run

sudo pacman -S gnome-keyring libsecret

Then reboot. Sign in should now work with most window managers. See here for additional details: https://wiki.archlinux.org/index.php/GNOME/Keyring

  • 👍93
  • 🎉23
  • ❤️27
  • 🚀13
  • 👀2
malteA commented

@Chuxel
Im using vanilla Arch with XFCE

I installed as you suggestet gnome-keyring and libsecret after a reboot it worked fine.

Thanks a lot.

  • 🎉19
LastLightSith commented

@malteA Checking out Arch, you likely don't have gnome-keyring and libsecret installed.

Run

sudo pacman -S gnome-keyring libsecret

Then reboot. Sign in should now work with most window managers. See here for additional details: https://wiki.archlinux.org/index.php/GNOME/Keyring

What about those on KDE

  • 👍33
GTpyro commented

I had a similar error occur using VS Code on Chrome OS when using the PostgreSQL extension by Chris Kolkman (ckolkman.vscode-postgres). The error prevented me from connecting to any database using the extension. I was able to resolve the error by installing the above two libraries via

sudo apt-get install gnome-keyring libsecret-1-0

(I'm writing this comment for any other poor soul who's using this obscure setup since this is the top search result for this error)

  • 👍10
  • 😕1
  • ❤️10
donutsahoy commented

This also fixed my issue with VS Code and Kubuntu 20.04.

  • 👍3
Ambyjkl commented

Hello, KDE user here. Will you ever implement KWallet support?

  • 👍30
  • 👀3
glittle commented

Installing the keyring solved a similar issue on a Chromebook linux with VS Code.

  • 👍1
Hamidalavi commented

@malteA Checking out Arch, you likely don't have gnome-keyring and libsecret installed.

Run

sudo pacman -S gnome-keyring libsecret

Then reboot. Sign in should now work with most window managers. See here for additional details: https://wiki.archlinux.org/index.php/GNOME/Keyring

Thank so much. you save my many times. Really useful command for solving this issue in KDE. before, i always have to login with gihub and configure my entries. thank again <3

1pavanb commented

Hello, KDE user here. Will you ever implement KWallet support?

Looks like it's not supported by KdeWallet, hasn't anything to do with VSCode supporting KdeWallet

microsoft/vscode-docker#1515 (comment)

thomas21120 commented

@malteA Checking out Arch, you likely don't have gnome-keyring and libsecret installed.

Run

sudo pacman -S gnome-keyring libsecret

Then reboot. Sign in should now work with most window managers. See here for additional details: https://wiki.archlinux.org/index.php/GNOME/Keyring

Thanks for the fix! saved me from manually setting up Vscode on another machine again. It is weird to me that I get this issue on Manjaro KDE with kernel 5.13 (only kernel my laptop wifi works on), but I do not have this issue on my desktop running Manjaro KDE kernel 5.10.

chainofflowers commented

For the ones using KDE and having this issue:
You can fix it even if you don´t (want to) use gnome-keyring but have another secrets provider installed - for instance, keepassxc. Just enable it (Tools|Setting|Secret Service Integration), and then click on the EDIT icon of your database in the "Manage" column. That will open the Database settings: there, click the "Secret Service Integration" icon and then "Expose entries under this group" - that will be the "wallet" or "keyring".

For reference: https://www.cogitri.dev/posts/03-keepassxc-freedesktop-secret/

  • 👍7