Vscode: Unable to install extensions [Linux]

[WhiskeyBeard]

• VSCode Version: Code 1.3.0 (e724f269ded347b49fcf1657fc576399354e6703, 2016-07-07T16:50:12.291Z)
• OS Version: Linux x64 4.4.0-28-generic

Steps to Reproduce:

1. Navigate to Extensions
2. Click Install on any extension, no call-outs to user, nothing happens.

[artem-sidorenko]

I also have difficulties to see the installed or outdated extensions

[Tyriar]

@WhiskeyBeard what distro are you on?

Also is anyone who :+1:'d experiencing this not on Linux?

[hyperlobic]

I am having these issues on Ubuntu 14.04.

[WasabiFan]

I'm seeing this on Ubuntu 15.04. I can't repro on any of my Windows machines. Notably, the dev console doesn't seem to indicate any errors that are thrown when I click the button, but every few seconds a bunch of errors are spewn independent of me trying to install extensions; no idea if it's related. See log of the first minute of VS Code running here.

[adam-mrachek]

Able to search extensions, but not able to install anything. Ubuntu 16.04

[mksarge]

Linux Mint 17.3
Like previous commenters - able to search extensions, but install button does nothing.
Dev console spawning periodic errors exactly like posted by @WasabiFan

[afluth]

Same issues. Ubuntu Gnome 16.04

[natsukagami]

Same issues on Arch Linux x64.

[ryanbowden]

Same issue ubuntu 14.04.

[joaomoreno]

Here are the 1.2.1 as a temporary workaround:

• 32bit archive
• 32bit deb
• 32bit rpm
• 64bit archive
• 64bit deb
• 64bit rpm

[DarkNekros]

I'm on Frugalware Linux x64 using the 64bit archive file and I've :+1: the ones that applies to me.

[joaomoreno]

Everyone, can you still reproduce with the downloadable archive?

32bit
64bit

[artem-sidorenko]

@joaomoreno it looks good for me

[ayanamist]

@joaomoreno No, it still has the issue on Ubuntu 14.04 with your provided archive.

[joaomoreno]

@ayanamist Do you have any extensions installed? Which? Could you zip up your extensions folder and send it to me?

[DarkNekros]

@joaomoreno not better for me :-1:

• Version 1.3.0
• Validation e724f269ded347b49fcf1657fc576399354e6703
• Date 2016-07-07T16:50:12.291Z
• Command Interpreter 0.37.6
• Converter 49.0.2623.75
• Node 5.10.0

I have this extensions:

• dbaeumer.jshint-0.10.12
• dbaeumer.jshint-0.10.15
• donjayamanne.githistory-0.0.6
• donjayamanne.python-0.3.10
• donjayamanne.python-0.3.17
• EditorConfig.EditorConfig-0.2.7
• EditorConfig.EditorConfig-0.3.0
• eg2.tslint-0.5.28
• eg2.tslint-0.5.32
• joelday.docthis-0.2.4
• joelday.docthis-0.3.1
• robertohuertasm.vscode-icons-1.1.5
• robertohuertasm.vscode-icons-1.3.4
• waderyan.gitblame-1.1.0
• zgudino.editorconfig-vscode-snippet-0.1.0

[joaomoreno]

@DarkNekros Do you have any extensions installed? Which? Could you zip up your extensions folder and send it to me?

[ayanamist]

@joaomoreno I have removed my extension from $HOME/.vscode/extensions, no better luck.

[jrobeson]

@joaomoreno : I'm using Fedora 24, and I'm still having the problem even when trying the versions you posted. I had extensions, but deleted them to reinstall them (but couldn't), so I can't provide them for you :(

[joaomoreno]

@ayanamist @jrobeson Both you guys still see this issue after wiping ~/.vscode/extensions?

[ayanamist]

@joaomoreno Yes, still have issue after wiping extensions dir.

[DarkNekros]

@joaomoreno sure :smile_cat: !

https://frama.link/vscode-extensions

[jrobeson]

@joaomoreno : yes I'd rm -rf ~/.vscode/extensions shortly after installing 1.3 the first time.

[devmetal]

@jrobeson Same problem here. I also deleted the folder, but it still not working on ubuntu 16

[joaomoreno]

@ayanamist & all:

Can someone set a breakpoint in extensionsWorkbenchService.ts:163 and trigger the bug? You can achieve this in the Developer tools, clicking Ctrl-O and typing extensionsWorkbenchService to find the file. I'm interested in the the contents of the t array, specifically if there are any extensions in there with an undefined manifest property:

[joaomoreno]

@ayanamist Would you be willing to do a live Skype debugging call with me?

[ayanamist]

i have got off my work and can not touch my laptop for several hours, sorry

[mquandalle]

I also encounter this bug. I set the breakpoint as indicated in https://github.com/Microsoft/vscode/issues/8859#issuecomment-231325130 but this code wasn't called when clicking on the “Install” button of the new extension panel.

Also, I don’t know if this is directly related but the console is full of the following error:

shell.ts:416 Cannot read property 'call' of undefined: TypeError: Cannot read property 'call' of undefined,
    at e.onCommonRequest (/usr/share/code/resources/app/out/vs/code/node/sharedProcessMain.js:6:20045),
    at e.onMessage (/usr/share/code/resources/app/out/vs/code/node/sharedProcessMain.js:6:19889),
    at /usr/share/code/resources/app/out/vs/code/node/sharedProcessMain.js:6:19697,
    at Socket.<anonymous> (/usr/share/code/resources/app/out/vs/code/node/sharedProcessMain.js:6:23531),
    at emitOne (events.js:90:13),
    at Socket.emit (events.js:182:7),
    at readableAddChunk (_stream_readable.js:153:18),
    at Socket.Readable.push (_stream_readable.js:111:10),
    at Pipe.onread (net.js:531:20)

e.onUnexpectedError @ shell.ts:416
(anonymous function) @ shell.ts:318
e.onUnexpectedError @ errors.ts:73
u @ errors.ts:88
(anonymous function) @ winjs.base.js:43
(anonymous function) @ winjs.base.js:38
winjs.base.js:45

[belst]

[RobertoMalatesta]

I have removed my extension from $HOME/.vscode/extensions, no better luck.

remove ~/.vscode as well with VSC shut.
use the zip version (uninstall the deb or whatever packaged version first)
run ./code --verbose

It worked at least for me, but I never installed the DEB one.

--R

[ayanamist]

@RobertoMalatesta when i comment it, i have no other directories in .vscode
i will try your method when i can touch my laptop.

[RobertoMalatesta]

@ayanamist it's a weird bug.
I did the same reasoning at first, then, seeing that .vscode was expendable since it was empty I nuked it.
Hth,

--R

[joaomoreno]

To whoever still sees this issue:

• Shutdown Code
• Run ps ax | grep code in a terminal, do you see any Code process still running?

[artem-sidorenko]

@joaomoreno yes, it was the case for myself. I killed all code processes before I tried the provided zips

[mquandalle]

It’s also the case for me:

$ ps ax | grep code
  716 ?        Ssl    0:44 /usr/share/code/code
  718 ?        S      0:00 /usr/share/code/code --type=zygote --no-sandbox
  979 ?        Sl     0:10 /usr/share/code/code /usr/share/code/resources/app/out/bootstrap --type=SharedProcess
 6417 ?        Sl     0:07 /usr/share/code/code /usr/share/code/resources/app/out/bootstrap git /home/mquandalle/github/push-notifications utf8 /usr/share/code/code 
26116 pts/6    S+     0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=.cvs --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn code

[DarkNekros]

@joaomoreno that's it!!! I had some code processes and after killing them, now it works :smiley:
Thank you for your time and effort to solve this issue :wink:

[joaomoreno]

Yeah great to know. I'm now investigating why it is that on Linux these processes stay alive for longer than expected.

[devmetal]

@DarkNekros Its worked me also. Thank you!

[WhiskeyBeard]

@joaomoreno Thanks for all the suggestions! I am on Ubuntu 16.04 LTS, but have workstations on Debian 8 Jessie also. I will try the kill process one when I get to the office. Hopefully that works, I will also try the debug session if needed. Let you know in a few.

[joaomoreno]

Workaround confirmed: kill all running code processes. Or simply restart your machine.

[puzzleflick]

my 2 cents..
on KDE-neon (based on ubuntu 16.04)... removing visual-studio code (sudo dpkg -r visual-studio-code) did the trick.

[karser]

I killed VSCode, and the extensions tab seems to be working on Ubuntu 14.04.

killall -9 code

[joaomoreno]

After a full day of debugging, here's the outcome. Thanks to all the people that reported the issue and helped reproduce it! Special thanks to @svarogg who did a Hangout session with me and helped me get some more clues on this mystery.

The bug: The shared process stays alive, after Code is shutdown.

It reproduces in Linux, 1.2.1 only with telemetry enabled. Does not reproduce in 1.1.1 nor 1.3.0.

The listening of SIGTERM within the shared process prevented it from shutting down whenever the main process sent that signal. It would then trust all the telemetry adapters to properly dispose which for some reason never happened.

This listener has been removed since, explaining why it can't be reproduced in 1.3.0.

Workaround

Kill all code processes OR restart machine.