I had the same problem before, in my case i need to add dbus-launch in .xinitrc to run dbus-session

• ~/.xinitrc

# init keyring
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
# export keyring
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

...

exec dbus-launch dwm

Upstream issue about this atom/node-keytar#132

I've updated the troubleshooting guide to point to the instructions from @maosid. Thanks!

Unable to Authorize Github what do I do?

Upstream issue about this atom/node-keytar#132

I've updated the troubleshooting guide to point to the instructions from @maosid. Thanks!

And those who doesn't use a gnome based system, like kubuntu?

Upstream issue about this atom/node-keytar#132
I've updated the troubleshooting guide to point to the instructions from @maosid. Thanks!

And those who doesn't use a gnome based system, like kubuntu?

Yup, I use Arch with Sway window manager, and this solution didn't fix the issue, I also tried this solution #92972 didn't fix it either

I am having the same/similar issue on Osx:

Writing login information to the keychain failed with error 'UNIX[No such file or directory]'.

@maosid what would be the code for KDE?

Upstream issue about this atom/node-keytar#132
I've updated the troubleshooting guide to point to the instructions from @maosid. Thanks!

And those who doesn't use a gnome based system, like kubuntu?

Yup, I use Arch with Sway window manager, and this solution didn't fix the issue, I also tried this solution #92972 didn't fix it either

I use Gentoo, had the same issue and resolved it by launching sway via dbus-run-session sway. Hope this helps someone.

For me, the error pops up after attempting to sign in, but signing in works regardless of the error.

Running Pop!_OS 21.04 and GNOME.

As a kludge, it's also possible to simply do:

dbus-launch code

The dbus-launch command sets some environment variables for the process that it spawns. If you are spawning a window manager in .xinitrc (ie dbus-launch dwm) then the entire GUI session will have those environment variables set.

If you run just dbus-launch at the cli, then you see the variables it is trying to set, ie:

> dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-sqROfzYKp1,guid=e9e634929ddff76d580cde8c618a3862
DBUS_SESSION_BUS_PID=30017

If you have launched your window manager from dbus-launch in .xinitrc or wherever, then you should be able to see those variables already existing by:

env | grep DBUS_SESSION_BUS

For those familiar with ssh-agent, this is the same concept.

I use Manjaro KDE, I can't fix the annoying problem, any help?

@julianperezpesce
I had the same problem with manjaro plasma
The problem was solved by :
Add the following lines to your ~/.xinitrc:

eval $(/usr/bin/gnome-keyring-daemon --start)

export SSH_AUTH_SOCK

mkdir -p "$HOME"/.local/share/keyrings```

`sudo pacman -S gnome-keyring libsecret libgnome-keyring`


install seahorse if dosen't exist .

Now restart vscode - he is work with me

Anyone on kde still facing the problem, simply install gnome-keyring

I'm on arch so sudo pacman -S gnome-keyring did the job

I'm facing the same problem, but the error message is different and that's why haven't tried any solutions for now...

any thoughts?

I'm facing the same problem, but the error message is different and that's why haven't tried any solutions for now... any thoughts?

Me too!

I'm facing the same problem, but the error message is different and that's why haven't tried any solutions for now... any thoughts?

Me too!

for me, surprisingly these steps worked out

Still facing the initial issue on artix(arch) even after installing gnome-keyring & libsecret and adding the above lines to my .xinitrc.
Any other solutions?

This error should not pop up at all if there is no settings sync configured to begin with. Don't tell me "But we need to check somehow". You should add a boolean into the setting disabling keychain access. If that means no settings sync -- that's fine.

This error should not pop up at all if there is no settings sync configured to begin with. Don't tell me "But we need to check somehow". You should add a boolean into the setting disabling keychain access. If that means no settings sync -- that's fine.

Wait that literally solves nothing though. I clearly have credentials I would like to save but none of the methods above solve it. I have isolated the issue and it seems dbus is having a hard time to start on boot. If I fix it, ill post something here.

How can I use KDE Wallet (kwalletd) instead? Gnome keyring does not integrate well into a KDE workstation.

I had the same problem before, in my case i need to add dbus-launch in .xinitrc to run dbus-session

* ~/.xinitrc

# init keyring
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
# export keyring
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

...

exec dbus-launch dwm

I am on Debian 11-updates/bookworm version (Antix Linux)
Adding throse lines ~/.xinitrc and reboot my laptop does not help me either.

Also I tested

 eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)

And

 eval $(/usr/bin/gnome-keyring-daemon --start)

Either of them gives error message:

 ** Message: 01:31:07.785: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

Anyone met similar issues?

Please, stop being opinionated how about Linux and keep vscode things on vscode code space, stop trying to use desktop services because Linux users are very diversified and everything was OK until now.

It's an improvement if they do it right and support all popular desktops and protocols.

I had the same problem before, in my case i need to add dbus-launch in .xinitrc to run dbus-session

* ~/.xinitrc

# init keyring
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
# export keyring
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

...

exec dbus-launch dwm

I am on Debian 11-updates/bookworm version (Antix Linux) Adding throse lines ~/.xinitrc and reboot my laptop does not help me either.

Also I tested

 eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)

And

 eval $(/usr/bin/gnome-keyring-daemon --start)

Either of them gives error message:

 ** Message: 01:31:07.785: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

Anyone met similar issues?

Yep same here on Artix s6 machine. I believe this is a problem with our setups and not VS Code itself, so we shouldnt be hoping for any over the top solution from the team.

I had the same problem before, in my case i need to add dbus-launch in .xinitrc to run dbus-session

* ~/.xinitrc

# init keyring
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
# export keyring
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

...

exec dbus-launch dwm

I am on Debian 11-updates/bookworm version (Antix Linux) Adding throse lines ~/.xinitrc and reboot my laptop does not help me either.
Also I tested

 eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)

And

 eval $(/usr/bin/gnome-keyring-daemon --start)

Either of them gives error message:

 ** Message: 01:31:07.785: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

Anyone met similar issues?

Yep same here on Artix s6 machine. I believe this is a problem with our setups and not VS Code itself, so we shouldnt be hoping for any over the top solution from the team.

Yes, I guess the best we can do is try whether we can fix this through discussions. The recent progress I met is I tried to add dbus-launch

dbus-launch /usr/share/code/code --unity-launch

The error message becomes

 Writing login information to the keychain failed with error 'Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached'.

Any idea how to fix this ?

I have the same issue on arch with i3, but i installed gnome and i tried it from there and somehow i could log in, both to sync settings and for github copilot.
Then switched back to i3 and it would not work.

I Think i found a "workaround", i opened VS Code, got the error message and exited. I reopened VS Code and waited for the "Unlock the default keyring" thing, typed in the password and it worked. Or im just delusional and they fixed it.

I had the same problem before, in my case i need to add dbus-launch in .xinitrc to run dbus-session

* ~/.xinitrc

# init keyring
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
# export keyring
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

...

exec dbus-launch dwm

I am on Debian 11-updates/bookworm version (Antix Linux) Adding throse lines ~/.xinitrc and reboot my laptop does not help me either.
Also I tested

 eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)

And

 eval $(/usr/bin/gnome-keyring-daemon --start)

Either of them gives error message:

 ** Message: 01:31:07.785: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

Anyone met similar issues?

Yep same here on Artix s6 machine. I believe this is a problem with our setups and not VS Code itself, so we shouldnt be hoping for any over the top solution from the team.

Yes, I guess the best we can do is try whether we can fix this through discussions. The recent progress I met is I tried to add dbus-launch

dbus-launch /usr/share/code/code --unity-launch

The error message becomes

 Writing login information to the keychain failed with error 'Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached'.

Any idea how to fix this ?

I have the same error message as you

see https://unix.stackexchange.com/a/295652/332452

source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh

see https://wiki.archlinux.org/title/GNOME/Keyring#xinitrc

eval $(/usr/bin/gnome-keyring-daemon --start)
export SSH_AUTH_SOCK

see NixOS/nixpkgs#14966 (comment)

mkdir -p "$HOME"/.local/share/keyrings

I'm getting Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached

Gentoo
awesomwm

I've added the stuff to xinitrc

Any idea about KDE Wallet instead of gnome-keyring?