Product and Version [VS/VSCode]: VSCode
OS Version [macOS/Windows]: KDE Neon User edition
Live Share Extension Version: v0.3.1156
Target Platform or Language [e.g. Node.js]:
Steps to Reproduce / Scenario:
might be related to this: https://github.com/MicrosoftDocs/live-share/issues/205
Screenshots

Hi , thank you for reporting this. Adding @legomushroom for investigation
once this is setup and is authorized under Applications -> Authorized OAuth Apps is the keyring stuffs needed anymore? im not sure if all of this is seamless on Gnome but on KDE its not very smooth.
is this related?
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/37
any update on this?
any update on this?
do you happen to also have Github Pull Requests installed along side Live Share?
after time of dealing with this it seems to be that it happens after every release that one needs remove the local keyrings dir, restart computer and then set password and login again until the next update is pushed.
i also dont seem to have this issue when solely using the pull requests extension, for example.
@jramsay looks like this issue still persists and never got resolved. Can we please take a look at this?
could those are are interested and still following please post their /etc/pam.d/sddm configurations?
Hey, we're looking at authentication issues for various workflows. We'll resume investigation here.
@kinghat mines empty
I had exactly the same problem in VSCode. This helped me.
Look into this https://www.fosslinux.com/2561/how-to-disable-keyring-in-ubuntu-elementary-os-and-linux-mint.htm
I think this is in no way a Live Share issue but rather lack of gnome-keyring integration in distro/DE. For example, I'm running Manjaro KDE and needed to follow this instruction from ArchWiki to get the keyring unlocked at login.
I have started facing the same issue after setting up OAuth for GitHub ( I was prompted to do it when I tried to publish a repo to GitHub). After that, every time I launch VS Code for first time on system boot, the pop up appears, since I have set up auto login for my Pop OS.
I believe this won't happen if I login to my user account manually instead of auto login, but it would be nice if we are given an option to avoid having to unlock keyring solely for VS Code.
I'm using Pop OS 20.04 GNOME and VS Code 1.48.0
Edit:
I'm not quite sure of why it happens, but here's my _theory_ : when you authorize VS Code to use your GitHub, VS Code stores the credentials to be used for next time, and these credentials are locked with your login keyring. Due to auto login, my keyring does not get unlocked at login. But VS Code needs the keyring to get unlocked in order to unlock your credentials. Hence the pop up.
How do we stop this from happening? I don't want config sync anymore
I tried all of these but nothing helped. Code keeps asking me to authenticate my keyring
trash-put $HOME/.vscode/extensions/*
trash-put $HOME/.config/Code/User/sync/globalState/
trash-put $HOME/.config/Code/User/sync/
trash-put $HOME/.config/Code/User/workspaceStorage/
trash-put $HOME/.config/Code/User/globalStorage/*
trash-put $HOME/.config/Code/Preferences
trash-put $HOME/.config/Code/Cache*
trash-put $HOME/.config/Code/Local\ Storage/*
trash-put blob_storage/
trash-put logs/
trash-put Session\ Storage/
trash-put Backups/
trash-put Code\ Cache/
trash-put Network\ Persistent\ State
trash-put Code
trash-put extensions/
I have received a popup to enter my password for my keyring every time I open a new vscode window. Disabling the liveshare extension solves this for me. I use liveshare very infrequently. I don't see why I can't disable this in the config.
Most helpful comment
Hey, we're looking at authentication issues for various workflows. We'll resume investigation here.