vscode: Github sign in not working on Linux
- VSCode Version: 1.52.1
- Electron: 9.3.5
- Chrome: 83.0.4103.122
- Node.js: 12.14.1
- V8: 8.3.110.13-electron.
- OS Version: Linux x64 5.4.0-58-generic (KDE Neon)
If I try to sign in to Github from VSCode, I get the usual Github authorization page in my browser, but after authorizing, when I paste the authorization token into VSCode (after clicking on “Signing in to github.com…”), nothing happens. It does not matter how I start the sign in process: from Settings Sync, from GitLens, by trying to pull from my Github repository, I experience the same.
The entry field disappears, and the Github Authentication Output prints “Treating input as token”, but the “Signing in to github.com…” text does not disappear from the status bar. I can click on it again, paste the token again, and the same happens over and over. It doesn’t matter how long I wait. I get neither an error message, nor any other output from the Github Authentication.
It was working earlier, until once I accidentally closed the window where I have to enter my password to unlock the keyring (which came up at every start of VSCode). Since then I experience the issue described above, and this window does not appear anymore either. I don’t if this is just a coincidence. I removed the appropriate key from the Gnome Keyring, but this had no effect.
Settings Sync is working with Microsoft account.
Steps to Reproduce:
- Start Github sign in from VSCode (e.g. from Settings Sync).
- Authorize on Github.
- If you don’t get redirected (which is the case for me), paste the token into VSCode.
- I don’t know… at this point basically nothing happens for me.
Does this issue occur when all extensions are disabled?: Yes
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (5 by maintainers)
In my case I was able to solve this by following the suggestion to temp change the default browser to Chrome and repeat the procedure.
The link workaround is working even on KDE, but maybe I will ask on Stack Overflow.
Anyways, thank you for your efforts. I think this issue can be closed.
Okay, I have reopened it.