No Keyring found, after update to 1.8

[RoccoRakete]

Describe the bug
Error message:
"An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment."
When trying to connect to github

Please confirm that this problem is VSCodium-specific

• [ X ] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• [ X ] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:
Trying to do any git actions related to a repository

Expected behavior
Cium should detect the keyring

Desktop (please complete the following information):

• OS: Arch Linux
• Architecture X64
• Version 1.80.0
• App Manager AUR
• Sandboxed no

The GitHub token is in fact stored in the keyring.

[slokhorst]

Same issue here, with a few remarks:

• This was introduced in 1.80.0, not 1.8
• This also happens with the Microsoft Visual Studio Code build
• If I click "Open troubleshooting guide", nothing happens

[RoccoRakete]

Same issue here, with a few remarks:

* This was introduced in 1.80.0, not 1.8

* This also happens with the Microsoft Visual Studio Code build

* If I click "show documentation", nothing happens

VSCode 1.80.0 is working perfectly fine for me.

[slokhorst]

Okay, my issue probably isn't a VS Code issue. It's just that my keyring isn't being autodetected.

After seeing the troubleshooting guide (not sure why I couldn't open that before), and using code --password-store="gnome", it works fine as before. I just remembered I had the same issue with Google Chrome, where I had to use the same command line argument to manually specify the password store to get it to work.

(I'm using Openbox with Gnome Keyring on Arch Linux.)

[szilvesztercsab]

Reproducible in VS Code version 1.80.0 on Debian 11 (bullseye) installed via official .deb package.

Plus, now my browser doesn't seem to open from VS Code anymore either.

Downgraded to 1.79.2 like so:

sudo apt install code=1.79.2-1686734195

...and it works again now.

---

Has to do with this ("In 1.80, we moved away from keytar, due to its archival, in favor of Electron's safeStorage AP").

---

But, I just couldn't live with a previous version, so I tried this (hardcoding "password-store": "gnome" in argv.json) and managed to fix the issue.

Thanks @slokhorst for pointing me in the right direction.

[BaigHack3rss]

But, I just couldn't live with a previous version, so I tried this (hardcoding "password-store": "gnome" in argv.json) and managed to fix the issue.

Thanks @slokhorst for pointing me in the right direction.

Editing the argv.json works!! I'd consider this issue closed.

[RoccoRakete]

But, I just couldn't live with a previous version, so I tried this (hardcoding "password-store": "gnome" in argv.json) and managed to fix the issue.
Thanks @slokhorst for pointing me in the right direction.

Editing the argv.json works!! I'd consider this issue closed.

Yep this does work.