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

Desktop environment wasn't detected (i3 with x11) #186792

Closed
goproslowyo opened this issue Jun 30, 2023 · 8 comments
Closed

Desktop environment wasn't detected (i3 with x11) #186792

goproslowyo opened this issue Jun 30, 2023 · 8 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@goproslowyo
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version:
$ code-insiders --version
1.80.0-insider
39efe30bfc8e196f5be2119479092bd9eb83e174
x64
  • OS Version:
$ cat /etc/os-release 
PRETTY_NAME="Ubuntu 23.04"
NAME="Ubuntu"
VERSION_ID="23.04"
VERSION="23.04 (Lunar Lobster)"
VERSION_CODENAME=lunar
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=lunar
LOGO=ubuntu-logo

Steps to Reproduce:

Following the request on https://github.com/microsoft/vscode-docs/blob/vnext/docs/editor/settings-sync.md#troubleshooting-keychain-issues to open a bug if my desktop environment wasn't detected. First off, if your desktop environment wasn't detected, please open an issue on VS Code with the verbose logs from above. This is important for us to support additional desktop configurations:

  1. VERBOSE1:key_storage_util_linux.cc(54)] Password storage detected desktop environment: (unknown)
    My setup is i3 with x11 running on Ubuntu 23.04.
@andreamah andreamah assigned TylerLeonhardt and unassigned andreamah Jul 4, 2023
@TylerLeonhardt TylerLeonhardt changed the title Desktop environment wasn't detected Desktop environment wasn't detected (i3 wuth x11) Jul 5, 2023
@TylerLeonhardt TylerLeonhardt changed the title Desktop environment wasn't detected (i3 wuth x11) Desktop environment wasn't detected (i3 with x11) Jul 5, 2023
@TylerLeonhardt
Copy link
Member

TylerLeonhardt commented Jul 5, 2023

Thanks for opening this. Just to check, using the docs were you able to unblock yourself by following the workaround steps:
https://github.com/microsoft/vscode-docs/blob/vnext/docs/editor/settings-sync.md#other-linux-desktop-environments

@deepak1556 I think this issue is for you but please let me know if you need me for anything.

@TylerLeonhardt TylerLeonhardt removed their assignment Jul 5, 2023
@goproslowyo
Copy link
Author

Thanks for opening this. Just to check, using the docs were you able to unblock yourself by following the workaround steps: microsoft/vscode-docs@vnext/docs/editor/settings-sync.md#other-linux-desktop-environments

@deepak1556 I think this issue is for you but please let me know if you need me for anything.

Hey @TylerLeonhardt -- yep using --password-store="gnome" works properly (and had added those to the argv.json file for the time being...). I do see gnome-keyring-daemon in the background and launching seahorse properly shows my keyring as well.

@Abastro
Copy link

Abastro commented Jul 7, 2023

Not the same setup, but I have the same problem with X11+XMonad on Ubuntu 23.04. I checked that gnome-keyring-daemon is running properly. Why is vscode trying to detect desktop environment here?

@TylerLeonhardt
Copy link
Member

@Abastro to determine what strategy to use to access the keyring on your machine. Can you and @goproslowyo please provide the full log output so we can see if there's anything else interesting in there?

@Jerry-Terrasse
Copy link

Hey @TylerLeonhardt, I'm encountered with the same issue on Manjaro 23.0.0 with i3wm.
here is my full log if it could help.

@TylerLeonhardt
Copy link
Member

Let's fold this in to #187338 since that has more comments and is the same root cause.

@TylerLeonhardt
Copy link
Member

/duplicate #187338

@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 10, 2023
@vscodenpa
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

7 participants