Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vscode 1.81.0 requires libsecret #248546

Closed
waldyrious opened this issue Aug 11, 2023 · 1 comment
Closed

vscode 1.81.0 requires libsecret #248546

waldyrious opened this issue Aug 11, 2023 · 1 comment
Labels
0.kind: bug Something is broken

Comments

@waldyrious
Copy link
Contributor

Describe the bug

Since 1.81.0, VSCode is prompting me with the following error:

You're running in a GNOME environment but the OS keyring is not available for encryption. Ensure you have gnome-keyring or another libsecret compatible implementation installed and running.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Install/upgrade vscode@1.81.0
  2. Open vscode
  3. See the error quoted above (screenshot below)

Expected behavior

No keyring-related error.

Screenshots

Screenshot from 2023-08-11 15-25-35

Additional context

The error message points to this troubleshooting page, but the instructions there didn't help me. Here is the log I get with the verbose command recommended there:

$ code --verbose --vmodule="*/components/os_crypt/*=1"

[1112331:0811/152809.984821:VERBOSE1:key_storage_util_linux.cc(54)] Password storage detected desktop environment: UNITY
[1112331:0811/152809.984837:VERBOSE1:key_storage_linux.cc(122)] Selected backend for OSCrypt: GNOME_ANY
[1112331:0811/152809.984986:VERBOSE1:libsecret_util_linux.cc(111)] Could not load libsecret-1.so.0: libsecret-1.so.0: cannot open shared object file: No such file or directory
[1112331:0811/152809.985003:WARNING:key_storage_linux.cc(177)] OSCrypt tried Libsecret but couldn't initialise.
[1112331:0811/152809.985101:WARNING:keyring_util_linux.cc(76)] Could not load libgnome-keyring.so.0: libgnome-keyring.so.0: cannot open shared object file: No such file or directory
[1112331:0811/152809.985113:WARNING:key_storage_linux.cc(190)] OSCrypt tried Keyring but couldn't initialise.
[1112331:0811/152809.985128:VERBOSE1:key_storage_linux.cc(142)] OSCrypt did not initialize a backend.

Searching for this online (or in this issue tracker) didn't yield many matches, but I did find this page in Japanese that seems to be working around a similar issue. Here's the google-translated version, in case it helps.

Notify maintainers

@eadwu @Synthetica @maxeaubrey @bobby285271 @Enzime

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.0-26-generic, Ubuntu, 22.04.3 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(waldir.pimenta): `"nixpkgs"`
 - nixpkgs: `/home/waldir.pimenta/.nix-defexpr/channels/nixpkgs`
@waldyrious waldyrious added the 0.kind: bug Something is broken label Aug 11, 2023
@waldyrious
Copy link
Contributor Author

waldyrious commented Aug 11, 2023

OMG. I searched the issues but forgot to search the PRs 🤦. This seems to have been fixed in #248167 — /CC @BlankParticle.

Oh well, at least hopefully the information above can help others locate the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

No branches or pull requests

1 participant