-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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 doesn't launch at all from the terminal (Ubuntu 15) after v0.10.8 #3131
Comments
@hashhar I'm assuming Launching using |
The absurd part is that clicking on the launcher I made ( see https://github.com/hashhar/vscode-universal-installer/blob/master/VSCode.desktop) launches it as it should. And both of them are using the same executable symlink. I'll try reproducing this on a VM. |
I can't reproduce this on other systems. Seems to be something wrong with my machine. My own machine can now not run any of the older releases too from the terminal. |
@hashhar ok, if you end up figuring it out please ping this issue as vscode may be able to warn/advise about the situation. |
@Tyriar Some more context. I cannot even start Code even if I build it locally. This is what happens. |
It only happens when I try to start it from the shell. Double clicking on the symlink as well as the executable launches it without problem. I even tried clearing Using a different Window Manager also didn't help. |
Yup. It's the SHELL. Using zsh also gave the error. But as soon as I set @Tyriar Maybe add this to the docs or FAQ. I'll try narrowing down the source of this. I was able to reproduce it on another install. This happens after some system updates. |
Works for every possible value of SHELL. It just doesn't work when SHELL=/bin/bash. This is a workaround but I would like a fix. This seems relevant. https://github.com/Microsoft/vscode/blob/master/src/vs/base/node/env.ts#L22 |
Interesting, I can run it just fine with |
It's not the terminal emulator. It's the shell that $SHELL is pointing to. Try setting $SHELL to /bin/bash or /bin/sh. |
It works when |
Thanks. Consider this closed then. A workaround is known atleast. |
All the system information is available in the image.
The text was updated successfully, but these errors were encountered: