I'm running vscode in an Ubuntu LXC container with Ubuntu host. Firefox is the default browser in the container. However links in vscode (for example, Help...Documentation) don't work. Nothing happens.
Perhaps there is a package I need to install?
Figured it out. Ran code --verbose and saw it was attempting an xdg-open. Installed xdg-utils. Viola!
Related
I installed VSCode from WSL (not WSL extention but normal Vscode linux app).
But when I try to view extentions - I am getting Error while fetching extentions. XHR failed.
There is a similar old bug: https://github.com/microsoft/vscode/issues/34385 . It is still open. But my case is different because I cannot see even extentions lists.
The solutions suggested are mainly around proxy settings but I am not behind proxy. I anyway tried them but nothing worked.
I tried different Ubuntu distros (22.04 and 18.04) - the same error.
I'm following the guide
and I am noticing that code tunnel -h in a ubuntu terminal window just launches the code UI.
Using the command palette to get the URI results in a tunnel to my Windows version of VSCode rather than the WSL:ubuntu (which is the one I care about)
How do I fix this?
It appears that, for now, you need to manually install the CLI in WSL in order for it to work. The downloads can be found here. Since you are on Windows, I would recommend the x64 CLI download. When you extract the tar.gz file, you will get a file named code. I would recommend moving it to your home directory for ease. To open the tunnel, run ./code tunnel (from wherever you put the code file) to force the new CLI. If you use code tunnel it will still use the Windows version.
Source: https://github.com/microsoft/vscode/issues/171196
Hey stackoverflow community i have an issue with vscode connecting to wsl2 with the following error [picture bellow] message i already searched for hours and couldnt find a solution.
reinstalled both with a clean updated version without any success
Edit 1:Tried to unmount and remount folders also tried opening with high privilege's from cmd 'wsl code .' moreover i completely deleted wsl and vscode with all the extensions but still am getting the same error, i was able to reproduce more readable error, when opening a project it prompts with
unable to resolve resource vscode-re...://%ubuntu-22.04/file_path
Edit 2: opening WSL, 'New WSL window using distro' works fine but i cant open any directory, without it producing the error in Edit 1
I got the same issue. I use Windows and I open the folder in vscode in this way:
shift+right-click the folder -> open linux shell -> type in "code ."
when vscode opens, the error does not exist.
For me this was due to the secondary sidebar being visible.
After disabling it via View -> Appearance -> Secondary Side Bar, WSL2 starts up fine again.
I got the same.
If your project is on another drive mount it and
run vscode as administrator.
I had this issue and needed to run..
$ code
Updating VS Code Server to version 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Removing previous installation...
Installing VS Code Server for x64 (97dec172d3256f8ca4bfb2143f3f76b503ca0534)
Downloading: 100%
Unpacking: 100%
Unpacked 2389 files and folders to /home/dmitri/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534.
in WSL2 to update the WSL2 server. Then uninstalling and reinstalling the WSL extension from VSCode did the trick.
I am the same.
I also reinstalled VSCode and Docker, but nothing changed.
In the "Remote - Containers" tutorial, I was able to connect without any problems.
It doesn't work with my code.
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.
I downloaded the latest ZIP file of VSCode for windows from VSCode website.
Unzipped it and tried running the Code.exe from it. It does nothing no crashing message juts output nothing.
I tried running Code.exe from command prompt [after CD to the directory where I have unzipped it], nothing happens, no out put.
Then I did some googling to do more troubleshooting and found out I need to run Code.exe or bin\code.cmd with --help and --verbose command.
No output on command line.
I am totally confused and don't know how do I make VScode work on my windows 7 machine or how do I troubleshoot why its not working.
I have appropriate .Net Framework installed [the one suggested by the VSCode website].
I have also tried installer , with all above debugging steps , same outcome as above.
I checked the code.exe in task manager to see if its running in background, nothing in there too.
What do I do ?
Check if the process is running in Task Manager.
Check for "code.exe". If it is running, then end all instances, and try again.
Otherwise, try opening event log, in Application or System. Look for errors or warnings which may have been logged and give some insight into why Code didn't open.
So guys seems like new version of VSCode has this problem.
Try downloading an older version of VSCode and do not upgrade it once its installed.
After I installed : V 1.18.1 , its working fine.