Code -OSS keyring issue

I am facing a problem in vs-code oss version…
And it is also related to keying…
And when i open vscode it shows something popup related to keyring (forgot to take screenshot)… and prompt to enter password.


“open troubleshoot guide” opens this link … but this is not quite relevant to me… cause i don’t use setting sync with any GitHub/Microsoft account …
also i use KDE …and i have disabled “Kwallet subsystem”

i also found…this

KDE 6 is not yet fully supported by Visual Studio Code. As a workaround: The latest kwallet6 is also accessible as kwallet5, so you can force it to use kwallet5 by setting the password store to kwallet5 as explained below in Configure the keyring to use with VS Code.

It’s possible that your wallet (aka keyring) is closed. If you open KWalletManager, you can see if the default kdewallet is closed and if it is, make sure you open it.

> verbose output as directed in this link

code --verbose --vmodule="*/components/os_crypt/*=1"
Gtk-Message: 22:56:30.658: Failed to load module "appmenu-gtk-module"
[8715:0811/] Floss manager not present, cannot set Floss enable/disable.
[main 2023-08-11T17:26:30.872Z] [File Watcher (node.js)] Request to start watching: /home/shanku/.config/Code - OSS/User (excludes: <none>, includes: <all>),/home/shanku/.config/Code - OSS/User/settings.json (excludes: <none>, includes: <all>)
[main 2023-08-11T17:26:30.898Z] Sending env to running instance...
[main 2023-08-11T17:26:30.900Z] [File Watcher (node.js)] Started watching: '/home/shanku/.config/Code - OSS/User'
[main 2023-08-11T17:26:30.901Z] [File Watcher (node.js)] Started watching: '/home/shanku/.config/Code - OSS/User/settings.json'
[8750:0811/] InitializeSandbox() called with multiple threads in process gpu-process.
[8750:0811/] dri3 extension not supported.
[main 2023-08-11T17:26:31.032Z] Sent env to running instance. Terminating...
[main 2023-08-11T17:26:31.033Z] Lifecycle#kill()
[main 2023-08-11T17:26:31.033Z]

Give a look at this:

Maybe install gnome-keyring and use the suggested workaround (I haven't read in detail about KDE).


gnome keyring is already installed

something with this??

Have you tried launching code with code --password-store="gnome" as suggested?

it actually works ...but i have to do it each time

The bug report also says that placing the property


in argv.json seems to work even though there is a warning generated that property is not allowed.

So I believe doing this would mean you don't have to pass command line params again. You can search online where this argv.json file is.

find / -iname "*argv.json*" -not -path '/.snapshots/*' 2> /dev/null

would do the trick
For me it was here


This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.