Change:
Name[ru]=Новое окно Name[zh_CN]=新建窗口 Name[zh_TW]=開新視窗 <del> Exec=/usr/share/@@NAME@@/@@NAME@@ --new-window %U </del> <ins> Exec=/usr/share/@@NAME@@/bin/@@NAME@@ --new-window %U </ins> Icon=@@NAME@@

Discussion:
VSCode Version: 1.3.1 OS Version: Ubuntu 16.04.1 LTS VM: VirtualBox 5.0.24 Host: Windows 10 Steps to Reproduce: Visual Studio Code from here: Paket by double click on .deb file VSCode via Ubuntu start menu Then a window opens. But it is completely black with some lighter (gray) squares as you can see here: ! I had a similar problem with google chrome. It could be fixed by disabling gpu on start up of chrome.
I hit the same issue under Fedora and VSCode 1.4 - the issue appears to be related to VirtualBox guest additions as described in . Rolling back to 5.0.16 fixed it.
Thanks for the advise. Actually running VS Code with solved the issue for me.
could you give our insider release a try to see if this issue is fixed? You can give our preview releases a try from:
Hi , sorry I cannot confirm that it is fixed for me. I recorded the behavior: !
thanks for giving this a try, seems to be an issue with VirtualBox.
Throwing my hat in the ring here, as I'm still seeing this issue. I'm running Ubuntu 16.10 with VS Code 1.9.1 - ). My symptoms are exactly the same as recorded. Running with verbose logging (sample):
Same issue here with code-insider 1.11.0-insider Starting code-insider on console works fine. But contains So the path part is missing in the file The script in the path adds an additional shell variable So setting is missing when is started directly from the file
can you check
does adding the in the path fix the problem? This was originally there as the application was behaving a bit weird when it came to pinning the desktop entry in Ubuntu. That appears to be fixed now though (after a quick test). You can try this yourself by changing the desktop entry in or something, then running and waiting a few seconds.
I'm using KDE Neon (Ubutnu 16.04 based distro) This problem only occurs with (). runs fine in all cases. Commands that work: Commands that DON'T work Clicking the icon and running the .desktop file does not work either The error message is always: 'Not working' means the window opens but there are no tabs or sidebar.

Just all black. Only the menu is on top but not functional. Ctrl+N does not open new tabs. Ctrl+B does not open the sidebar. I searched for error logs but did not find any. Toggle developer tools is working, but there are no logs in the console tab. The DOM-Elements tab shows an almost empty body-tag and no div with class monaco-shell-content. If there are any log-files you know about let me know and I will send them.
Ok I found how to reproduce it. The last line in my is But you can use or as well as last line. Opening a second shell in the seems to be the cause for this behaviour. As mentioned before this is new in . No problems with .
launching through the dash in Ubuntu shouldn't trigger though? Technically but only to fetch the shell environment, but that shouldn't cause anything like this. Do you think adding bin/ to the .desktop file would resolve the issue?
Yes adding helps. It sounds weird and it shouldn't source the but somehow it does. I tested it on a fresh ubuntu 16.04 install in a virtual box with code and code-insiders (without extensions). And it is reproducible. Adding as last line to the does prevent code-insiders from a proper startup when clicking on the desktop icon. The current code version 1.10.2 runs fine.
The desktop entry now uses the bin/ script.
I reverted this change due to It you're running into this due to running another program in your .bashrc I recommend either detecting the environment you're running in or if it's a shell, change .