vscode: Can't turn on setting sync, Error while turning on Settings Sync. No authentication providers are available.

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: visual-studio-code-bin 1.65.0-1
  • OS Version: Manjaro kde

Steps to Reproduce:

  1. install vscode through yay from AUR
  2. open it and try to trun on settings sync
  3. Click on the account button but there is no reaction.
  4. try to trun on setting sync from start page, and it will say: “Error while turning on Settings Sync. No authentication providers are available.”

In all , I can’t turn on settings sync using github account or microsoft account.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 9
  • Comments: 31 (10 by maintainers)

Most upvoted comments

I also had the exact same problem after applying the same update in Arch Linux. I solved by installing gnome-keyring libsecret libgnome-keyring.

I used the official deb package from the VS Code website, and I am getting the same error. @sandy081

Error while turning on settings sync. No authentication providers...

Installing gnome-keyring via apt solves the issue. It seems gnome-keyring should be included as a dependency in the .deb package.

I also had the exact same problem after applying the same update in Arch Linux. I solved by installing gnome-keyring libsecret libgnome-keyring.

Wow, that’s work for me too. Eventhrough my desktop application is kde. thank you very much. But I wonder is that the correct solutions to this issue. it does make sync work again, but it tell me to set and store a new keyring which i never came across before.

@TylerLeonhardt Ok so I had to enable gnome-keyring daemon and it works fine.

@wiredhikari my guess is that the keyring isn’t getting unlocked or the secret service provided by libsecret isn’t launching properly… you may have to do some digging around awesome wm & libsecret or gnome-keyring. I’ll try to do some digging on my side but you might have more context than I since you have context on awesome wm.

Ya sure I will try figuring it out and let you know how it goes.

It’s a tough one because gnome-keyring isn’t a dependency… our dependency is "anything that implements org.freedesktop.secrets API which is gnome-keyring, kwallet, or KeePassXC…

gnome-keyring is the easiest to set up but not everyone wants that.