XMING + Putty on Windows 10 cannot launch VSCODE

[pdewilde]

I am running putty on windows 10 configured to xforward using xming

$ xclock works as expected
but if I do
$ code
I get

[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
code: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted

and nothing shows up.

This is different from #13438 as it is not using WSL.

[Tyriar]

Are you trying to run the Linux version of VS Code under Windows via xming?

[pdewilde]

Correct. I am running a Windows 10 machine and using putty with x11 forwarding to ssh into a remote machine. Xming is the xserver on the local Windows machine. I want to work on a remote linux host, and x-forwarding VS Code seemed like a more practical solution than setting up sshfs and ssh to get files and terminal to point to the remote version.

To be more specific, the linux host is running CentOS 7.4.1708 (Core)

I do not have root permissions on the remote machine, so I installed vscode using the tar in my home directory. Currently I am running version VS Code 1.15.0, but could update if you think that would be helpful.

[Tyriar]

Unfortunately we do not support launching VS Code using an X server for similar reasons to why launching in WSL doesn't work. When there is movement on #13138, support for this may be improved.

[pdewilde]

Word on the stack overflow grapevine is that VcXsrv works. I'll test it and report back.

[pdewilde]

VcXsrv gives the same error behavior.