I have been using VSCode for a while and never had any big problem with it. Today I tried to start my VSCode from left taskbar on my Ubuntu 18.04 and it not showing up. Also, I tried to run in terminal as 'code .' again nothing.
VSCode version is latest 1.23.1 I tried few time today with install/remove and nothing. Somehow I am thinking maybe it something with permissions but not sure.
When click on task bar icon its shows like loading on top taskbar in ubuntu 18.04 for a few seconds and stops.
Also when tried to run in terminal as:
$ code . --verbose
[15027:0603/191139.702752:ERROR:browser_main_loop.cc(279)] Gtk: Locale not supported by C library.
Using the fallback 'C' locale.
[15027:0603/191139.809312:ERROR:browser_main_loop.cc(279)] Gtk: GModule (/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization check failed: GLib version too old (micro mismatch)
[15027:0603/191139.809326:ERROR:browser_main_loop.cc(279)] Gtk: Loading IM context type 'ibus' failed
pcilib: Cannot open /sys/bus/pci/devices/0000:07:00.0/resource: No such file or directory
just getting an error, but not sure is this error connected with problem I did some investigation and Gtk is already installed and works well on my OS.
Fixed it with "delete the /home/user/.config/Code folder"
https://github.com/Microsoft/vscode/issues/55774#issuecomment-412774473
Related
I constantly use MS VS code for remote development and it is overall a great IDE. But I noticed that extensions that I use all the time (python and juypyter) stop working suddenly, from time to time.
I have the two extensions installed locally:
When connected to a remote SSH, I see that they appear not to be installed on the remote server (which is, again, something new, as they were installed just yesterday)
When I click on the icon to install them on the remote server I get:
a pop-up screen on the bottom right corner:
Also on the log terminal I see:
[2022-07-07 14:52:48.576] [remoteagent] [info] Getting Manifest... ms-toolsai.jupyter
[2022-07-07 14:52:48.639] [remoteagent] [error] Failed to install extension. ms-toolsai.jupyter
[2022-07-07 14:52:48.639] [remoteagent] [error] Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:220:20)
which unfortunately is not all that informative.
I also tried to install via the small download/ cloud button on the left-hand side panel:
Yet it does not work either.
Does anyone know the background of this error/ why the extensions stopped working suddenly? NB from yesterday to today (when the extensions stopped working), VS code was not upgraded. Does this look like a bug, so that a bug report should be filled to their github page?
Local OS is Ubuntu 20.04 LTS, remote is CentOS Linux 8. VS code version is:
1.68.1
30d9c6cd9483b2cc586687151bcbcd635f373630
x64
I have been struggling with this vs code issue (extension host terminated unexpectedly).
I've tried uninstalling/ reinstalling vs code, I've uninstalled and disabled all my extensions and still get the error, I've downloaded an older version which worked temporarily, I'm out of ideas.
I don't understand how I can have no extensions but the still get the error?
does anybody know the answer to this?
it seems I'm having the same issue as your from around the same time. I would suggest to add more infos, in my case for example
> MacOS X : 10.11.6 El Capitan
> VS Code Version: 1.57.1
> Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
> Date: 2021-06-17T13:28:32.912Z
> Electron: 12.0.7
> Chrome: 89.0.4389.128
> Node.js: 14.16.0
> V8: 8.9.255.25-electron.0
> OS: Darwin x64 15.6.0
After a long period of not using VS Code I found this alert always popping up
-Extension host terminated unexpectedly
-Open Developer Tools -Restart Extension Host
And restarting just repeated this alert.
If I choose from the context menu (aka right click) Run a line/selection or Run Current File, either on terminal or in interactive window with Jupyter, it has no reaction (while a couple of days ago it worked perfectly, when I used it in offline cause there was no wifi)
In hope it could help you, here are what I tried:
to deactivate and reactivate the extension (cmd+shift+p > Reload With
Extensions disabled)
to install a previous extension of Python ms-python.python (or whatever suit your case)
to run the command Bisect (cmd+shift+p > Help: Start Extension
Bisect)
So far I found no solution for me.
Soon I will try to follow what sumitparakh commented in this github issue , meaning to save the former extensionHostProcess.js file (renaming it) and adding in its stead the file he provided
On Windows the location should be
C:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js
While MacOS path should be:
'/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js'
UPDATE 1: after adding the file and reloading I get even this message
-Your Code installation appears to be corrupt. Please Reinstall
-More information
UPDATE 2: I tried to follow this fix from a github issue . Here is the quote:
ehamwey commented on Jan 4
The following steps worked for me, after upgrading from an x86 build
of vscode-insiders to Darwin arm64 (version 1.53.0-insider) I got the
behavior described above.
Remove the folder: /Users/[your-home-folder]/.vscode/ # **NOTE:** I renamed it as a backup
This will remove all extensions and any vscode configurations from your system!
Reinstall vscode and any extensions
BUT, even after I reinstalled the same version 1.57.1 of Code the extension host error is there, without any extension yet installed...
So maybe, I should try to revert to a previous update and maybe even reporting this issue
I'm open to suggestion aswell
I solved it running in the notebook kernel:
pip install six
Good day community. I have installed VS Code in my MacBook Air M1 chip running on BigSur 11.3.1 but whenever I set the code command in PATH (using Command+Shift+P) it only appears to be working for current session and doesn't work if I restart VSCode. I have to set the code command in PATH again. Please help me in configuring code command permanently so that i can open VSCode from any directory whenever I want. Thanks
I think I have got the solution. After installing VSCode in your Mac (which will be in download folder) move VS Studio Code.app file to Application Folder and then again install the code command in PATH from VSCode(using Command+Shift+P) and thats it.
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 am using CentOS 7.7.1909 version.
I installed vscode via yum, the window pops up but nothing comes up like the screenshot. What should I do?
Try running it from the command line with the following flag:
code --disable-gpu
The Electron shell used by Visual Studio has trouble with some GPU hardware acceleration.