Open Konglomneshued opened 1 year ago
For users who had "password-store": "gnome"
stopped working, can you please help test whether it works again in the following build
VS Code Build: 59fb28097d54d21729e591ed8af0e4de8fb53ea2
linux-arm64 linux-armhf linux-x64
Steps to test:
code-insiders --user-data-dir /tmp/test-argv-check
"password-store": "gnome"
in argv.jsonFor users who had
"password-store": "gnome"
stopped working, can you please help test whether it works again in the following buildVS Code Build: 59fb280
linux-arm64 linux-armhf linux-x64
Steps to test:
- Extract and run the build with
code-insiders --user-data-dir /tmp/test-argv-check
- Set
"password-store": "gnome"
in argv.json- Confirm that authentication works as expected.
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 DE: Xfce 4.18 it's work: yay -S gnome-keyring kate ~/.vscode/argv.json and paste "password-store": "gnome-libsecret" reboot sync settings vscode
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 /bin/python /home/jackokring/.vscode/extensions/ms-python.python-2024.4.0/python_files/printEnvVariablesToFile.py /home/jackokring/.vscode/extensions/ms-python.python-2024.4.0/python_files/deactivate/bash/envVars.txt
in the terminal context. The terminal should behave like a system terminal and not be a proxy for lazy exec programming.
Chromebook. arm64.
OS: Endeavouros 64 DE: Lxqt need to add "password-store": "gnome-libsecret" to ~/.vscode/argv.json to fix this problem.
OS: Endeavouros 64 DE: Lxqt need to add "password-store": "gnome-libsecret" to ~/.vscode/argv.json to fix this problem.
i use "password-store": "basic", it's work after reboot on xfce 4.18
I'm using Vscode 1.92.2 on Ubuntu 24.04 and had a similar issue where vscode would hang up when it tried to connect to the internet
This was the last line in the log before vscode hang up:
main 2024-08-26T14:13:58.031Z] [EncryptionMainService] Checking if encryption is available...
For me, "password-store": "basic"
fixed it. Thanks @als-creator
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: 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:
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.