An OS keyring couldn't be identified

[oliben67]

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

• VS Code Version: 1.104.2
• OS Version: Pop!_OS 24.04 LTS with the COSMIC desktop (beta) with seahorse (based on Ubuntu 24.04)
• details:
  Version: 1.104.2
  Commit: e3a5acf
  Date: 2025-09-24T11:21:37.073Z
  Electron: 37.3.1
  ElectronBuildId: 12404162
  Chromium: 138.0.7204.235
  Node.js: 22.18.0
  V8: 13.8.258.31-electron.0
  OS: Linux x64 6.16.3-76061603-generic

Steps to Reproduce:

1. from command line : $ code --verbose --vmodule="/components/os_crypt/=1"

[10807:0927/181538.578464:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: (unknown)
[main 2025-09-27T16:15:38.669Z] [File Watcher (node.js)] Request to start watching: /home/osteck/.config/Code/User (excludes: , includes: , filter: , correlationId: ),/home/osteck/.config/Code/User/settings.json (excludes: , includes: , filter: , correlationId: )
[main 2025-09-27T16:15:38.676Z] Sending env to running instance...
[main 2025-09-27T16:15:38.677Z] [File Watcher (node.js)] Started watching: '/home/osteck/.config/Code/User'
[main 2025-09-27T16:15:38.677Z] [File Watcher (node.js)] Started watching: '/home/osteck/.config/Code/User/settings.json'
[10846:0927/181538.710067:WARNING:sandbox/policy/linux/sandbox_linux.cc:415] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2025-09-27T16:15:38.717Z] Sent env to running instance. Terminating...
[main 2025-09-27T16:15:38.718Z] Lifecycle#kill()
[main 2025-09-27T16:15:38.718Z] Lifecycle#onWillShutdown.fire()

2. Desktop environment is detected as unknown. Since the desktop environment Cosmic is brand new - beta - no real surprise but the OS is based on Ubuntu 24.04 nonetheless (same keyring manager seahorse)

Looking at https://source.chromium.org/chromium/chromium/src/+/main:base/nix/xdg_util.cc GetDesktopEnvironment() seems to not detect COSMIC although the environment is already registered in the code base

[dwc13]

Ran across same issue.
Fresh Arch Linux install with COSMIC Desktop Environment.

Version: 1.104.2
Commit: e3a5acf
Date: 2025-09-26T19:07:51.304Z
Electron: 37.5.1
ElectronBuildId: undefined
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.16.8-arch3-1

$ code --verbose --vmodule="*/components/os_crypt/*=1"
[15249:0928/232444.391477:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: (unknown)
[main 2025-09-29T04:24:44.505Z] [File Watcher (node.js)] Request to start watching: /home/dom/.config/Code - OSS/User (excludes: <none>, includes: <all>, filter: <none>, correlationId: <none>),/home/dom/.config/Code - OSS/User/settings.json (excludes: <none>, includes: <all>, filter: <none>, correlationId: <none>)
[main 2025-09-29T04:24:44.512Z] Sending env to running instance...
[main 2025-09-29T04:24:44.513Z] [File Watcher (node.js)] Started watching: '/home/dom/.config/Code - OSS/User'
[main 2025-09-29T04:24:44.513Z] [File Watcher (node.js)] Started watching: '/home/dom/.config/Code - OSS/User/settings.json'
[15285:0928/232444.532048:WARNING:sandbox/policy/linux/sandbox_linux.cc:415] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2025-09-29T04:24:44.569Z] Sent env to running instance. Terminating...
[main 2025-09-29T04:24:44.569Z] Lifecycle#kill()
[main 2025-09-29T04:24:44.570Z] Lifecycle#onWillShutdown.fire()

[dwc13]

After doing some more reading in the VSCode documentation.

I went ahead and installed the kwallet packages (including the kwalletmanager for a gui), created and opened a wallet. Then following the VSCode doc, added this line to config -- "password-store": "kwallet5", and saved. Make sure to unlock the wallet.

Restarted Code, and was able to sign into my account without getting an error.

Possibly an issue with COSMIC's seahorse keyring application not being recognized, but is odd since other applications are able to use it.

[brianary]

Same issue.

Pop!_OS 24.04 LTS with the COSMIC desktop (beta) with seahorse (based on Ubuntu 24.04)

Version: 1.105.1
Commit: 7d842fb
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.16.3-76061603-generic

[main 2025-10-27T02:54:06.604Z] [EncryptionMainService] Checking if encryption is available...
[6172:1026/195406.605006:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: (unknown)
[6172:1026/195406.605019:VERBOSE1:components/os_crypt/sync/key_storage_linux.cc:116] Selected backend for OSCrypt: BASIC_TEXT
[6172:1026/195406.605039:VERBOSE1:components/os_crypt/sync/key_storage_linux.cc:135] OSCrypt did not initialize a backend.
[main 2025-10-27T02:54:06.605Z] [EncryptionMainService] Encryption is available: false

My XDG_SESSION_DESKTOP environment variable is set to COSMIC, which seems like it should be detected correctly.

[theking2]

Same here on Fedora 43 Budgie.

Version: 1.105.1
Commit: 7d842fb
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.6-300.fc43.x86_64

In Seahorse the login key is unlocked. Passwords and Keys v47.0.1

[main 2025-11-05T22:05:02.299Z] [EncryptionMainService] Checking if encryption is available...
[69562:1105/230502.300033:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: (unknown)
[69562:1105/230502.300042:VERBOSE1:components/os_crypt/sync/key_storage_linux.cc:116] Selected backend for OSCrypt: BASIC_TEXT
[69562:1105/230502.300080:VERBOSE1:components/os_crypt/sync/key_storage_linux.cc:135] OSCrypt did not initialize a backend.
[main 2025-11-05T22:05:02.300Z] [EncryptionMainService] Encryption is available:  false
[69562:1105/230502.304346:INFO:CONSOLE:36] "%cTRACE color: #888 [SecretStorageService] Encryption is not available, falling back to in-memory storage", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (36)
[69562:1105/230502.304507:INFO:CONSOLE:36] "%cTRACE color: #888 [secrets] getting secret for key: secret://{"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (36)
[69562:1105/230502.304671:INFO:CONSOLE:36] "%cTRACE color: #888 [secrets] no secret found for key: secret://{"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (36)
[69562:1105/230502.304840:INFO:CONSOLE:36] "%cTRACE color: #888 [mainThreadSecretState] No password found for:  vscode.github-authentication github.auth", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (36)

[axiopaladin]

I can confirm it persists into the 24.04 Pop!_OS Cosmic b1 release

[Nwyfre]

Also seeing the issue on CachyOS

[juanmagomez16]

Same on Fedora 43 Cosmic desktop

Version: 1.106.2
Commit: 1e3c50d
Date: 2025-11-19T16:56:50.023Z
Electron: 37.7.0
ElectronBuildId: 12781156
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.8-300.fc43.x86_64

Log:
4684:1122/203504.090381:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: (unknown) [4722:1122/203504.236421:WARNING:sandbox/policy/linux/sandbox_linux.cc:415] InitializeSandbox() called with multiple threads in process gpu-process. [main 2025-11-23T01:35:04.251Z] PolicyConfiguration#initialize

[saloid]

Same:
Pop!_OS 24.04 LTS x86_64 + COSMIC
seahorse 43.0

# code --verbose --vmodule="*/components/os_crypt/*=1"
[22951:1125/131538.014411:VERBOSE1:key_storage_util_linux.cc(51)] Password storage detected desktop environment: (unknown)