-
Notifications
You must be signed in to change notification settings - Fork 30.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VirtualBox: VSCode showing an empty window after installation on Ubuntu #10091
Comments
I hit the same issue under Fedora and VSCode 1.4 - the issue appears to be related to VirtualBox guest additions as described in this thread. Rolling back to 5.0.16 fixed it. |
Thanks for the advise. Actually running VS Code with |
@battermann @vocoded could you give our insider release a try to see if this issue is fixed? |
Hi @bpasero , sorry I cannot confirm that it is fixed for me. I recorded the behavior: |
@battermann 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 - f9d0c68). My symptoms are exactly the same as @battermann recorded. Running with verbose logging (sample):
|
Same issue here with code-insider 1.11.0-insider
But
So the The script in the
So setting |
@Tyriar can you check #10091 (comment) |
@internetz does adding the You can try this yourself by changing the desktop entry in |
I'm using KDE Neon (Ubutnu 16.04 based distro)
This problem only occurs with
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. |
Ok I found how to reproduce it. The last line in my
But you can use |
@internetz launching through the dash in Ubuntu shouldn't trigger Do you think adding bin/ to the .desktop file would resolve the issue? |
Yes adding It sounds weird and it shouldn't source the |
The desktop entry now uses the bin/ script. #24523 |
I reverted this change due to #24961 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 |
Steps to Reproduce:
Then a window opens. But it is completely black with some lighter (gray) squares as you can see here:
Remark
I had a similar problem with google chrome. It could be fixed by disabling gpu on start up of chrome.
Verbose CLI output
The text was updated successfully, but these errors were encountered: