-
Notifications
You must be signed in to change notification settings - Fork 28.7k
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
Missing or invalid credentials. Error: connect ENOENT /run/user/1000/vscode-git-6fc6e74986.sock #192551
Comments
I've tried to logout and login again, as well as restart the computer |
The issue seems to be fixed now, after I've totally closed the directory and open it again (with only a restart it was not working). Sorry, you guys can ignore this issue. |
I have like 50 changes and there was this error showing like authentication failed Error: connect ENOENT /run/user/1000/vscode-git-fb00d917e3.sock i closed the vs code and restarted the directory again it worked fine |
Same here in latest stable version. |
It's still randomly happens to me |
My env is win10 + WSL2(ubuntu 22.04) + vscode 1.82.2 |
similar situation. ubuntu 22.04 + vscode 1.82.2 |
I don’t know if this is really a bug of VS CODE. Maybe it’s a bug of Ubuntu itself, because /run/user/1000 will be deleted entirely inexplicably. My WSL has enabled systemd. My current solution is run sudo loginctl enable-linger username then restart wsl |
@deepak1556, does this ring a bell? |
Can affected users check if the issue is present with out latest insiders https://code.visualstudio.com/insiders, I feel this might be a side effect of #192742 |
had the same problem with /run/user/1000, and this solution worked for win11 + WSL2(ubuntu 22.04) + vscode 1.83 |
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
I'm not good at steps to reproduce, but it was working before the latest update,
All my nodejs projects are not able to do git pull or push, even if I can see the changes made.
I'm on ubuntu 22.04 with node 19.5.
Sorry but I cannot provide more info
The text was updated successfully, but these errors were encountered: