-
Notifications
You must be signed in to change notification settings - Fork 29.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
Core dump: Windows 10 machine running Xming as an X server #840
Comments
I honestly don't know if we support this setup. |
Any updates regarding this? Got this error too today trying the same setup (using ubuntu 16.04). I happened to stumble across this in a google search for a solution. |
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders |
Hey bpasero, I downloaded the tar.gz inside file (code-insider-1.6.0-1475776934_amd64.tar.gz). I extracted it and ran "./code-insiders" I got gmalenko@ubuntu:~/VSCode-linux-x64$ ./code-insiders I'm going to do the deb file and see how it goes Installed deb file. Run "code-insiders" from the command prompt and nothing really happens. It appears that a process does start gmalenko@ubuntu:~/VSCode-linux-x64$ ps -aux | grep code I'm sure if I booted into Ubuntu it would work fine on that machine. Is there a reason why it doesnt work using putty and xming? Other apps such as firefox will work fine. Should I just make this a new issue? |
Same here, currently nothing happens : $ ./code &
[1] 16395 ubuntu 16.04 gest (vagrant) / windows 10 host |
I encountered the same issue. Simply extracted the code-stable-code_1.6.1-1476373175_amd64.tar.gz & call ./code, then got the same error. [cash@ubuntu1404 VSCode-linux-x64]$./code |
The same issue. I downloaded the tar.gz and then:
|
@b1es @PunchyRascal Got the same issue, but it is not related to vscode, I got the same one with atom. I assume than you are not using a windows 10 insider build, but win10 anniversary update as I do. This is due to shutdown not being implemented for sockets. Though it is already fixed for insider builds: microsoft/WSL#758 |
Yes, like you say. But I reverted to using samba-connected linux share on windows, which is rather slow, but otherwise it has pretty much the best native feel anyway. |
same issue here |
I ran into the same problem with Win7 and Xming. Later I tried to VcXsrv and it worked with that. |
When I try to start code in Ubuntu 14.04, using my local Windows 10 machine running Xming as an X server, code crashes before I even see a window.
~$ code &
[2] 7847
~$ bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
/bin/VSCode-linux-x64/Code: ../../src/xcb_io.c:274: poll_for_event: Assertion
!xcb_xlib_threads_sequence_lost' failed. cd vscode/ [2]+ Aborted (core dumped) code (wd: ~) (wd now: ~/vscode) ~/vscode$ code . & [2] 7949 ~/vscode$ bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. /bin/VSCode-linux-x64/Code .: ../../src/xcb_io.c:274: poll_for_event: Assertion
!xcb_xlib_threads_sequence_lost' failed.ls
[2]+ Aborted (core dumped) code .
The text was updated successfully, but these errors were encountered: