Linux: An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment #187338
Comments
|
I tried to setup the runtime args according to the support article I listed: |
|
Can you please include the very top of the logs? The part that contains the stuff call out here: https://code.visualstudio.com/docs/editor/settings-sync#_linux Or even the whole log works. |
|
Additionally, what desktop environment & window manager are you using? |
|
For me this is happening on i3 on arch, also using gnome keyring. Adding the |
Uh.. sorry I'll try to find the log file if they are kept. Also I'm using a similar setup as GerritPlehn, i3 on Arch. |
|
Here is the main.log if that's the one you need. |
|
Related: #186792 Chromium failing to detect i3 seems to be the common thread |
TylerLeonhardt
added
upstream
|
Getting the same error as well on bspwm. |
|
Same issue on Sway and my gnome-keyring-daemon is correctly set-up. Launching code with |
|
Same issue here, using Ubuntu 23.04 with i3wm. |
|
Same for me. i3wm on Manjaro 23.0.0 |
|
Same for me, using EndeavourOS 6.4.1-arch2-1 and qtile. |
|
Same issue with an i5, and Version: 1.80.0 Also getting this, even though it seems to be working: |
TylerLeonhardt
changed the title
|
Something like this will help in a lot (if not all) of these cases and is something that we'll need in Electron. That said, i3 might be big enough to be a detected environment which is why I haven't duped this to that issue. |
|
I'm seeing this issue as well on Arch running XMonad. |
|
I am also seeing this on Arch with XMonad using 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 Finally, |
|
Same happening on Arch with awesomewm. Adding |
deepak1556
added
bug
|
Same happening for me on Sway after upgrade to 1.86.0 |
|
I've just tried setting "gnome-libsecret" instead of "gnome" and everything works again! |
|
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. |
|
Same happening for me just after upgrading to |
|
Fixed by setting |
This does not work for me. |
It worked for me on Arch, thanks! |
|
|
|
Still the same problem (on Manjaro). |
|
Switching from Version: 1.86.0 |
|
If you are in a situation where |
|
On ChromeOS, I get that error too
Which is weird, because Is it due to the behavior change you're talking about @deepak1556? Update: yes (see #187338 (comment))
// This configuration file allows you to pass permanent command line arguments to VS Code.
// Only a subset of arguments is currently supported to reduce the likelihood of breaking
// the installation.
//
// PLEASE DO NOT CHANGE WITHOUT UNDERSTANDING THE IMPACT
//
// NOTE: Changing this file requires a restart of VS Code.
{
// Use software rendering instead of hardware accelerated rendering.
// This can help in cases where you see rendering issues in VS Code.
// "disable-hardware-acceleration": true,
// Allows to disable crash reporting.
// Should restart the app if the value is changed.
"enable-crash-reporter": true,
// Unique id used for correlating crash reports sent from this instance.
// Do not edit this value.
"crash-reporter-id": "d3649379-71f0-49b8-8896-22d26592c978",
"password-store": "gnome",
}
malix@penguin:~$ sudo apt install gnome-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
gnome-keyring is already the newest version (42.1-1+b2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.malix@penguin:~$ code --verbose --vmodule="*/components/os_crypt/*=1"
[0205/162123.944602:ERROR:file_io_posix.cc(152)] open /home/malix/.config/Code/Crashpad/pending/c863bb7a-4d1c-4761-ac18-81dba03f53a8.lock: File exists (17)
[3708:0205/162124.111662:VERBOSE1:key_storage_util_linux.cc(52)] Password storage detected desktop environment: (unknown)
[3708:0205/162124.161114:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2024-02-05T15:21:24.331Z] [File Watcher (node.js)] Request to start watching: /home/malix/.config/Code/User (excludes: <none>, includes: <all>, correlationId: <none>),/home/malix/.config/Code/User/settings.json (excludes: <none>, includes: <all>, correlationId: <none>)
[main 2024-02-05T15:21:24.365Z] Sending env to running instance...
[main 2024-02-05T15:21:24.367Z] [File Watcher (node.js)] Started watching: '/home/malix/.config/Code/User'
[main 2024-02-05T15:21:24.370Z] [File Watcher (node.js)] Started watching: '/home/malix/.config/Code/User/settings.json'
[3742:0205/162124.388037:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2024-02-05T15:21:24.505Z] Sent env to running instance. Terminating...
[main 2024-02-05T15:21:24.505Z] Lifecycle#kill()
[main 2024-02-05T15:21:24.505Z] Lifecycle#onWillShutdown.fire()malix@penguin:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"VS Code Version: 1.86.0 - 0504748 - x64 |
Breaking Fixvscode = 1.86.0 |
|
Are there any resources on what other OS keyrings could be used other than gnome-keyring? EDIT: That would be here: https://code.visualstudio.com/docs/editor/settings-sync#_recommended-configure-the-keyring-to-use-with-vs-code |
gnome-libsecret is not a package I could find. Do you mean |
|
For users who had VS Code Build: 59fb280 linux-arm64 Steps to test:
|
Can confirm that this build fixed the issue for me. |
|
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 |
|
Looks like an update has fixed the issue for me. My config is still: "password-store": "gnome-libsecret" |
|
OS: ArcoLinux x86_64 but I’m wondering if it’s possible to get rid of this problem altogether, why do we need a keychain in this editor, and is it possible to somehow simplify this action? if this is only needed to sync settings, then there must be an easier way |
|
I'm using seahorse. Have you added the default "login" keystore? Not sure if it's needed. Added "password-store": "gnome-libsecret" and after collapsing the side nav bar it (the april release) no longer locks up and works (after overnight). VSCode should not be issuing git commands through the terminal session. VSCode should not be running Chromebook. arm64. |
|
OS: Endeavouros 64 |
i use "password-store": "basic", |
and others
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":Version: 1.81.0-insider
Commit: ad791ef
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:
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.
The text was updated successfully, but these errors were encountered: