I have installed vscode on my ubuntu machine.
Opening it up and choosing Terminal -> New terminal opens up an integrated terminal. However, there is just a white marker where the working directory should be, and it is completely unresponsive. I have read the vscode troubleshooting and search here, but can find anything about it. What is wrong? See image of unresponsive terminal below.
Related
Currently have to manually write source ./zshrc to get my zsh plugins to work within the vscode terminal window, however I dont have this issue if I open a zsh shell outside of vscode. I am using Debian on wsl2.
In terminal I get proper syntax example (due to a plugin)
However in vscode I dont unless i run source ./zshrc
As seen here:
Every time I try to open the terminal in VSCode it immediately fails with this error:
I tried uninstalling re-installing vscode, and disabled all my extensions, but it still happens. There is nothing I've changed right before it started occurring.
Colleagues in my organization do not suffer from this so I don't know if it has something to do with our IT dept.
the version of vscode I use is 1.70.0
my default terminal is Powershell. It does work when changing the default terminal to CMD.exe
Opening Powershell on its own does work properly.
Currently on Ubuntu I'm running KDE version 5.18.8, and I've just started coding in Visual Studio Code, but when toggling the console, I just get an old notification on the top right corner of my screen informing me how old it is, not using the shortcut entirely.
*(I toggled the terminal manually in the settings)
Is this a shortcut I have to change in vscode or KDE? Since there isn't anything online I can seem to find for this. It's a bit of an annoyance.
I don't know what happen, but I was working on VSCODE in windows adding neovim path to the settings.json.
I clicked inside the settings.json and vscode started to open new editor tabs by itself with the same content of settings.json.
I have uninstalled vscode several times, removed the Appdata roaming vscode, the Appdata local code, etc. I installed the vscode again and same behavior. I restarted my windows machine and same behavior.
The sync is on so the settings replicates to all my vscode installations. I started my Linux machine to see if this was something that replicated to my linux version. No, it is working normal.
I can work on VScode if I don't open the settings. It has open new editors (clones of settings) upto 500 hundred times.
I was able to stop it when I changed directory and it asked me if I wanted to close and all open tabs. The moment that I go to settings starts again.
You could start to not sync extentions. Maybe one is breaking it.
But You could also try to install an older version of vs code.
How to downgrade vscode
Hi I'm running Linux Mint 19 and I have just installed vscode using the snapd package manager. I've not used vscode on linux before as my usual editor is emacs. However, on a fresh new install of vscode, the integrated terminal does not work, there is just a non blinking cursor in the top left of the screen, but no prompt and no keyboard strokes are registering. This appears to be a common problem as there are a lot of posts about it if googled, but they are all for Windows versions and none of the solutions that I'm able to try do anything. I've tried to open a new terminal window, but the same thing happens I just get two terminal windows that I now cannot use. I've also tried checking the box that says Code-runner: Run In Terminal, but that does nothing either. What can I do to get this to work please, I looks to me like it is just not connected to either a bash or Zsh(which I normally use). Any help on this would be appreciated.
Instead of starting vscode with its default shell script (usually located on /usr/share/code/bin/code), the integrated terminal only works for me when starting it directly from the compiled binary (typically found on /usr/share/code/code, which is the same as the launcher created by the installer:
/usr/share/code/code --no-sandbox --unity-launch %F
While I searched for a solution in the past I've also noticed that lots of folks solved similar problems just by adding --disable-gpu flag, so might be worth checking out as well.