vscode: Linux: An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment
Does this issue occur when all extensions are disabled?: Yes
I referred to https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues
This is the error part of my log after running code-insiders --verbose --vmodule="*/components/os_crypt/*=1"
:
[314774:0707/210405.156953:INFO:CONSOLE(627)] "%cTRACE color: #888 [mainThreadSecretState] Setting password for vscode.github-authentication extension: github.auth", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210405.157113:INFO:CONSOLE(627)] "%cTRACE color: #888 [NativeSecretStorageService] Notifying user that secrets are not being stored on disk.", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210405.158116:INFO:CONSOLE(627)] "%cTRACE color: #888 DialogService#prompt An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment.", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.420345:INFO:CONSOLE(627)] "%cTRACE color: #888 [secrets] encrypting secret for key: {"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[main 2023-07-08T02:04:09.420Z] [EncryptionMainService] Encrypting value.
[main 2023-07-08T02:04:09.422Z] Error: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.
at e.$U2b.encrypt (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:42:11004)
at Object.call (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:25:4844)
at R.s (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:23:5128)
at R.q (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:23:4644)
at o.value (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:23:4051)
at y.w (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1906)
at y.x (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1976)
at y.fire (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:2192)
at o.value (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:16:38681)
at y.w (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1906)
at y.fire (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:2123)
at o.value (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:16:38875)
at y.w (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1906)
at y.fire (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:2123)
at se (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:16:41018)
at IpcMainImpl.f (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:19:96358)
at IpcMainImpl.emit (node:events:513:28)
at EventEmitter.<anonymous> (node:electron/js2c/browser_init:2:80979)
at EventEmitter.emit (node:events:513:28)
[314774:0707/210409.425211:INFO:CONSOLE(627)] "%c ERR color: #f33 Error: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.425442:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Getting accounts for github", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.425641:INFO:CONSOLE(627)] "%c INFO color: #33f Settings Sync: Updated current session 8103a56381b60bac", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.425835:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Getting accounts for github", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.426026:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Updated accounts for github", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.426214:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Getting accounts for microsoft", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.426428:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Updated accounts for github", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.426630:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Getting accounts for microsoft", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.426816:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Updated accounts for microsoft", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.426981:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Updating the token for the account Android789515", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.427124:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Token updated for the account Android789515", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.427693:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Updated accounts for microsoft", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.427861:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Updating the token for the account Android789515", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.428010:INFO:CONSOLE(627)] "%cTRACE color: #888 Settings Sync: Token updated for the account Android789515", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
Version: 1.81.0-insider Commit: ad791ef3d26b99963da31636af697afd86575435 Date: 2023-07-07T19:47:36.821Z Electron: 22.3.14 ElectronBuildId: 21893604 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Linux x64 6.4.1-arch2-1
I have gnome-keyring installed and it’s not using it for some reason. Must be the update to 1.80.
Manually configuring the keyring to use results in this:
code-insiders --password-store="gnome"
Warning: 'password-store' is not in the list of known options, but still passed to Electron/Chromium.
It seems to work.
I figured this is a bug since I had gnome-keyring installed, it wasn’t being used, and I had to manually configure it.
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 48
- Comments: 108 (12 by maintainers)
Same happening on Arch with awesomewm. Adding
"password-store": "gnome"
to~/.vscode/argv.json
fixed the issue.I’ve just tried setting “gnome-libsecret” instead of “gnome” and everything works again! @Android789515 can you try it too?
I tried to setup the runtime args according to the support article I listed:
Same issue on Sway and my gnome-keyring-daemon is correctly set-up.
Launching code with
code --password-store="gnome"
as suggested here works.Same happening for me just after upgrading to
1.86.0
. Fixed by settinggnome-libsecret
instead ofgnome
!Hey @pavelxdd, your suggestion worked for me. Thank you!
However, I find it strange that the VS Code docs say this:
This implies that the default behavior should work, but it doesn’t seem to.
I am also seeing this on Arch with XMonad using
gnome-keyring
.This did not fix it:
This did:
System info:
For reference, if helpful, in such systems it’s common to start xmonad in this manner (this is my
.xinitrc
):Finally,
gnome-keyring
is initialized on login via PAM:Can this be fixed for the infinite number of users having this problem? Seems like every time someone installs vscode he has to open this thread
Same for me. i3wm on Manjaro 23.0.0
Same issue with an i5, and
"password-store": "gnome"
fixes it.Version: 1.80.0 Commit: 660393deaaa6d1996740ff4880f1bad43768c814 Date: 2023-07-04T13:39:48.236Z Electron: 22.3.14 ElectronBuildId: 21893604 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Linux x64 5.15.108-18910-gab0e1cb584e1
Also getting this, even though it seems to be working:
Property password-store is not allowed.
inargv.json
If you are in a situation where
"password-store": "gnome"
in argv.json no longer works, sorry for the breakage there was a behavior change in the runtime that got missed in the runtime update. Bothgnome
andgnome-keyring
values are removed in favor ofgnome-libsecret
. We will prepare a candidate fix for1.86.1
release.For those with NixOS, I spotted that there’s now a fix in
master
while investigating this (Thanks @BlankParticle): https://github.com/NixOS/nixpkgs/commit/ed2f5f18292f238762fde3a2076ee727c029e917(Also, hint for others can be to check your
LD_LIBRARY_PATH
, turned out mine was messed up so I had to fix that too)I just write the argv.json and call it a day
I am using
visual-studio-code-bin 1.81.0-1
from AUR and setting:in
argv.json
works. Of course, for this to work, you need to install and setup gnome-keyring-daemon. The guide I used.Same happening for me on Sway after upgrade to 1.86.0 I have “password-store”: “gnome” in argv.json which no longer works.
This is no longer working for me.
My config:
What I see:
Can confirm that manually adding
"password-store": "gnome"
to theargv.json
file worked (on Arch Linux, BSPWM, VSCode 1.80.1).Had to add the arg manually after running code with
code --password-store="gnome"
failed to work.Same happening on Ubuntu 22.04 with i3wm. Adding
"password-store": "gnome"
to~/.vscode/argv.json
fixed the issue.Also happens on Chromebook. The
password-store
workaround did the trick.Same issue on Debian 11 (ChromeOS)/aarch64 with version 1.80
argv.json password-store: gnome workaround successful.
From #187436.
I’m using
archlinux
withhyprland
as desktop environment. To manage my keyring I have installedkwallet
.The pop-up disappear when I set
password-store
tokwallet5
.Additionally I’ve configured dbus to start the service automatically by creating the file
/usr/share/dbus-1/services/org.freedesktop.secrets.service
with the content:I don’t know if it’s possible for vscode to use the service configured in
org.freedesktop.secrets
as keyring manager 🤔I’m seeing this issue as well on Arch running XMonad.
Looks like an update has fixed the issue for me.
My config is still:
Can confirm that this build fixed the issue for me.
Solution if you’re using a non-popular window manager
gnome-keyring libsecret
. On arch you can runsudo pacman -S gnome-keyring libsecret
code --password-store="gnome"
@sashap8 can you open a separate issue? It’s probably not related to Linux.
When you open it, please follow the troubleshooting steps to make sure that you include the necessary information.
Ask 10 Persons, and you get 15 answers…here we go:
on i3 will also do the job. Just checked on my Arch Linux i3 Desktop.
That didn’t work for me, as well as many people in this thread, if the solution was that simple, I wouldn’t have gone through the trouble of trying 20 previous versions until I found a working one.
Same issue with sway on Arch Linux. According to this doc it seems we indeed need to setup the keyring. What I did:
gnome-keyring
(since it wasn’t installed by default with sway)"password-store"="gnome"
in.vsode/argv.json
or--password-store=gnome
in.config/code-flags.conf
Quite annoying to have to install gnome-keyring (or whatever supported keyring).
Came here, to say thank you for the workaround, facing the same issue on Arch + Sway.
Adding
"password-store": "gnome"
to~/.vscode/argv.json
worked for me on Fedora 37 with i3wm.Fedora/i3wm, same issue.
It seems that last VsCode update broke everything for everyone not using a “standard” Linux distribution.
Same issue with Manjaro/i3 here, and the flag fixed it for me but is not satisfying
Got the same error in Xfce4, using
gnome-keyring
Adding
"password-store": "gnome"
to~/.vscode/argv.json
solved it.I am using:
Same for me, using EndeavourOS 6.4.1-arch2-1 and qtile.