VS Code detects KDE instead of GNOME for password store #415

TheOnlyTails · 2023-07-24T21:06:11Z

Ever since the last update, something broke which causes VSC to show an error like this at startup:

This causes me to be forcibly logged out of settings sync. Problem is, I use Gnome and have been using it for months.

What is going on?

Note: I've tried this resource: https://code.visualstudio.com/docs/editor/settings-sync#_other-linux-desktop-environments but to no avail.

SeaDve · 2023-07-25T12:17:16Z

Adding "password-store": "gnome-libsecret" in argv.json as a workaround works for me

TheOnlyTails · 2023-07-25T13:09:03Z

Does nothing for me, unfortunately.

francoism90 · 2023-08-05T16:06:14Z

@SeaDve Where is this file located?

SeaDve · 2023-08-05T16:07:44Z

@SeaDve Where is this file located?

Run Preferences: Configure Runtime Arguments command

francoism90 · 2023-08-05T16:14:41Z

@SeaDve This doesn't work for me, it also gives me Property password-store is not allowed..

AlbertoFabbri93 · 2023-08-05T19:04:11Z

I have tried adding both "password-store": "gnome-libsecret" and "password-store": "gnome" in argv.json but neither works.

irfanhakim-as · 2023-08-09T03:08:54Z

@SeaDve This doesn't work for me, it also gives me Property password-store is not allowed..

In my case, it had given me the same warning in argv.json but it worked nonetheless.

In any case, try launching VS Code this way first for logging as well as for testing the workaround:

flatpak run com.visualstudio.code --verbose --vmodule="*/components/os_crypt/*=1" --password-store=gnome-libsecret

If the issue is solved, you can proceed to add "password-store": "gnome-libsecret" to argv.json so the behaviour persists without the additional flag.

If it doesn't, close VS Code and check the logs for errors.

Note: In my case, I am indeed using KDE Plasma and kwallet5 on my system instead of Gnome and gnome-keyring unlike the OP. I did get the exact same error and behaviour, which was solved by using the earlier mentioned workaround.

AlbertoFabbri93 · 2023-08-09T21:44:51Z

@irfanhakim-as Thank you for the help!

As before, it does not work for me. This is what I found in the log:

[23:0809/233425.828199:VERBOSE1:key_storage_linux.cc(174)] OSCrypt using Libsecret as backend.
[23:0809/233425.832975:VERBOSE1:key_storage_libsecret.cc(82)] OSCrypt generated a new password.
[23:0809/233425.833799:INFO:CONSOLE(627)] "%cTRACE color: #888 Layout#layout, height: 1048, width: 1920", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[main 2023-08-09T21:34:25.834Z] window#load: window reported ready (id: 1)
[main 2023-08-09T21:34:25.834Z] ElectronURLListener#flush(): flushing URLs
[23:0809/233425.864152:INFO:CONSOLE(627)] "%cTRACE color: #888 [secrets] getting secret for key: secret://vscode.loginAccount", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[23:0809/233425.864483:INFO:CONSOLE(627)] "%cTRACE color: #888 [secrets] no secret found for key: secret://vscode.loginAccount", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[main 2023-08-09T21:34:25.864Z] Going to get password from keytar: vscode.login account
[main 2023-08-09T21:34:25.868Z] Doing get password from keytar: vscode.login account
[main 2023-08-09T21:34:25.869Z] Did not get a password from keytar for account: account

quocson95 · 2023-08-26T10:27:54Z

In my case, set argv.json ""password-store": "gnome-libsecret"" and install "zypper install gnome-keyring", then vscode work (sync with github)

mscharley · 2023-09-28T11:00:05Z

I'm actually running KDE but ran into this and while the editor tab for argv.json complains that password-store isn't a valid property, "password-store": "gnome-libsecret" does get picked up and work for connecting to kwallet (and presumably any other libsecret backend) for me. It does seem to use different keys in kwallet now as i had to sign in again, but the new sign in is remembered across restarting vscode.

breningham · 2023-11-06T13:46:57Z

using your command @irfanhakim-as i notice the following issue:

[24:1106/134215.090087:INFO:CONSOLE(630)] "%cTRACE color: #888 ChatService#constructor: Restored 1 persisted sessions", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)
[24:1106/134215.096507:INFO:CONSOLE(630)] "%cTRACE color: #888 [SecretStorageService] Encryption is available, using persisted storage", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)
[24:1106/134215.096601:INFO:CONSOLE(630)] "%cTRACE color: #888 [secrets] getting secret for key: secret://{"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)
[24:1106/134215.096658:INFO:CONSOLE(630)] "%cTRACE color: #888 [secrets] decrypting gotten secret for key: secret://{"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)
[main 2023-11-06T13:42:15.096Z] [EncryptionMainService] Decrypting value.
[24:1106/134215.096902:VERBOSE1:os_crypt_linux.cc(238)] Decryption failed
[main 2023-11-06T13:42:15.097Z] Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.
    at D.decrypt (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:42:11339)
    at Object.call (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:25:4881)
    at I.s (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:23:5128)
    at I.q (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:23:4644)
    at c.value (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:23:4051)
    at w (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:1913)
    at w.x (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:1983)
    at w.fire (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:2199)
    at c.value (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:16:38683)
    at w (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:1913)
    at w.fire (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:2130)
    at c.value (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:16:38878)
    at w (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:1913)
    at w.fire (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:18:2130)
    at Z (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:16:41008)
    at IpcMainImpl.f (/app/extra/vscode/resources/app/out/vs/code/electron-main/main.js:19:96477)
    at IpcMainImpl.emit (node:events:513:28)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:88527)
    at WebContents.emit (node:events:513:28)
[24:1106/134215.105346:INFO:CONSOLE(630)] "%c  ERR color: #f33 Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)
[24:1106/134215.105416:INFO:CONSOLE(630)] "%cTRACE color: #888 [mainThreadSecretState] No password found for:  vscode.github-authentication github.auth", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)
[24:1106/134215.105472:INFO:CONSOLE(630)] "%cTRACE color: #888 [mainThreadSecretState] Getting old password for vscode.github-authentication extension:  github.auth", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (630)

seems that it finds the values but fails to decode them for some reason.

OKRUgit · 2023-11-22T17:08:30Z

дело было так!
Раньше этой ошибки небыло, точнее в KDE окружении небыло. Была другая ошибка: бумажник KDE по умолчанию всегда отключали и жили спокойно, и никому это не мешало.
Однако при первом заходе мучали ключи другого окружения от GNOME. Так это и работало ставились ключи от GNOME потом эти ключи в системе удалялись и больше оно не беспокоило, от слова совсем. Шутка, небыло значит не надо.

С недавнего времени эти ключи добавились после очередного обновления, добавили проверку ключей и в ларужении KDE.

Предпологаю: опять надо обманывать систему.
Пробую старый способ: активировать(или установить) связку ключей от GNOME потом один раз заполнить пустые пароли, благополучно эти ключи снести из системы и жить как раньше.

Если сработает конечно.
Эти проблемы только микромягких, это им кажется что нападение неизбежно из-за вырявости системы, вот они и маются бедьняги, защищаются...

Писал себе такое https://yvsik.ru/forum/topic/c%d0%b2%d1%8f%d0%b7%d0%ba%d0%b0-%d0%ba%d0%bb%d1%8e%d1%87%d0%b5%d0%b9/

теперь надо находить как от этих ключей збавляться.

OKRUgit · 2023-11-22T17:24:22Z

даже манул предлогает это сделать, .

Если вы используете KDE5 или выше и у вас возникают проблемы с подключением к kwallet5 (например, у пользователей неофициального пакета VS Code Flatpak в выпуске # 189672), вы можете попробовать настроить связку ключей на gnome-libsecret, поскольку при этом для связи с любой действующей связкой ключей будет использоваться Secret Service API. kwallet5 реализует API секретной службы и может быть доступна с помощью этого метода.

francoism90 · 2023-11-22T17:42:43Z

Yeah, I'll not click on any of the provided links.

OKRUgit · 2023-11-22T18:42:18Z

скажу больше, если почитать что они там пишут
https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues
то вы убедитесь слово (рекомендует) звучит странно. Рекомендовано не значит должно быть!!! Скажем по желанию,
Тут же все наоборот, если рекомендовано, значит обязательно!
И тут же: цитирую
"### (рекомендуется) Настройте связку ключей для использования с VS Code.
Вы можете вручную указать VS Code, какой набор ключей использовать, передав флаг password-store. Мы рекомендуем сначала установить gnome-keyring, если у вас его еще нет, а затем запустить VS Code с code --password-store="gnome"."
Ссылка на ресурс-> https://code.visualstudio.com/docs/editor/settings-sync#_other-linux-desktop-environments

Что они там курят (эти микро мягкие)и кто их просит?
И между всего прочего эти связки все отключат но упрямо их заставляют использовать. Не всртечал ни одного кто ими пользуется и это как то помогало. Кроме постоянного ввода паролей в две прграммы VScode(теперь ) и ранее в chrome , теже вилы!

OKRUgit · 2023-11-25T00:57:02Z

Всё, сам справился ,а вы?
https://yvsik.ru/forum/topic/c%D0%B2%D1%8F%D0%B7%D0%BA%D0%B0-%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%B9/#postid
Читаем последний пост Написано не очень понятно, пока делал писал что было необходимо , чтоб не запутаться.
Но теперь программа больше не требует вводить пароль.
Работает с ключами от GNOME и чувствует себя спокойно
бумажник KDE в системе отключен.

Только дергается к сайту GitHub, надо на сайте тоже согласиться атоматизировать и все ...

SeaDve mentioned this issue Aug 5, 2023

Flatpaked VSCode 1.80.1 cannot sync #417

Open

TylerLeonhardt mentioned this issue Aug 8, 2023

You're running in a KDE environment but the OS keyring is not available for encryption. Ensure you have kwallet running. microsoft/vscode#189672

Closed

Dryadxon mentioned this issue Nov 7, 2023

Error while decrypting the ciphertext provided to safeStorage.decryptString flathub/com.vscodium.codium#239

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VS Code detects KDE instead of GNOME for password store #415

VS Code detects KDE instead of GNOME for password store #415

TheOnlyTails commented Jul 24, 2023 •

edited

Loading

SeaDve commented Jul 25, 2023

TheOnlyTails commented Jul 25, 2023

francoism90 commented Aug 5, 2023

SeaDve commented Aug 5, 2023 •

edited

Loading

francoism90 commented Aug 5, 2023

AlbertoFabbri93 commented Aug 5, 2023

irfanhakim-as commented Aug 9, 2023 •

edited

Loading

AlbertoFabbri93 commented Aug 9, 2023

quocson95 commented Aug 26, 2023

mscharley commented Sep 28, 2023

breningham commented Nov 6, 2023

OKRUgit commented Nov 22, 2023 •

edited

Loading

OKRUgit commented Nov 22, 2023 •

edited

Loading

francoism90 commented Nov 22, 2023

OKRUgit commented Nov 22, 2023

OKRUgit commented Nov 25, 2023 •

edited

Loading

VS Code detects KDE instead of GNOME for password store #415

VS Code detects KDE instead of GNOME for password store #415

Comments

TheOnlyTails commented Jul 24, 2023 • edited Loading

SeaDve commented Jul 25, 2023

TheOnlyTails commented Jul 25, 2023

francoism90 commented Aug 5, 2023

SeaDve commented Aug 5, 2023 • edited Loading

francoism90 commented Aug 5, 2023

AlbertoFabbri93 commented Aug 5, 2023

irfanhakim-as commented Aug 9, 2023 • edited Loading

AlbertoFabbri93 commented Aug 9, 2023

quocson95 commented Aug 26, 2023

mscharley commented Sep 28, 2023

breningham commented Nov 6, 2023

OKRUgit commented Nov 22, 2023 • edited Loading

OKRUgit commented Nov 22, 2023 • edited Loading

francoism90 commented Nov 22, 2023

OKRUgit commented Nov 22, 2023

OKRUgit commented Nov 25, 2023 • edited Loading

TheOnlyTails commented Jul 24, 2023 •

edited

Loading

SeaDve commented Aug 5, 2023 •

edited

Loading

irfanhakim-as commented Aug 9, 2023 •

edited

Loading

OKRUgit commented Nov 22, 2023 •

edited

Loading

OKRUgit commented Nov 22, 2023 •

edited

Loading

OKRUgit commented Nov 25, 2023 •

edited

Loading