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!

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

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

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

@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 personally gave up using copilot because of this.

Any idea about KDE Wallet instead of gnome-keyring?

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.

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

@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

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 https://github.com/NixOS/nixpkgs/issues/14966#issuecomment-520083836

mkdir -p “$HOME”/.local/share/keyrings

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

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?

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.

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.