Skip to content
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

Closed
jakeoshins opened this issue Nov 30, 2015 · 11 comments
Closed

Core dump: Windows 10 machine running Xming as an X server #840

jakeoshins opened this issue Nov 30, 2015 · 11 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@jakeoshins
Copy link

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 .

@bpasero bpasero changed the title Starting code results in core dump Core dump: Windows 10 machine running Xming as an X server Dec 1, 2015
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Dec 1, 2015
@bpasero bpasero added this to the Backlog milestone Dec 1, 2015
@bpasero
Copy link
Member

bpasero commented Dec 1, 2015

I honestly don't know if we support this setup.

@bpasero bpasero closed this as completed Dec 22, 2015
@bpasero bpasero added the verified Verification succeeded label Jan 26, 2016
@gmalenko
Copy link

gmalenko commented Oct 6, 2016

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.

@bpasero
Copy link
Member

bpasero commented Oct 7, 2016

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

@gmalenko
Copy link

gmalenko commented Oct 7, 2016

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
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.
ome/gmalenko/VSCode-linux-x64/code-insiders: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

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
gmalenko 24259 18.0 5.2 866912 53000 ? Ssl 14:46 0:00 /usr/share/cod -insiders/code-insiders
gmalenko 24261 2.5 2.9 309164 30080 ? S 14:46 0:00 /usr/share/cod -insiders/code-insiders --type=zygote --no-sandbox
gmalenko 24265 0.0 0.0 14224 932 pts/0 S+ 14:46 0:00 grep --color=auto 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?

@uael
Copy link

uael commented Oct 23, 2016

Same here, currently nothing happens :

$ ./code &
[1] 16395

ubuntu 16.04 gest (vagrant) / windows 10 host

@cashlalala
Copy link

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
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.
roj/cash/VSCode-linux-x64/code: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

@b1es
Copy link

b1es commented Nov 7, 2016

The same issue. I downloaded the tar.gz and then:

$ ./code

[516:1107/131853:FATAL:render_sandbox_host_linux.cc(40)] Check failed: 0 == shutdown(renderer_socket_, SHUT_RD). shutdown: Invalid argument
#0 0x000001e0962e <unknown>
#1 0x000001e1f23b <unknown>
#2 0x000001e1f7fd <unknown>
#3 0x000002892e52 <unknown>
#4 0x00000265e2f9 <unknown>
#5 0x0000026648bf <unknown>
#6 0x00000265d996 <unknown>
#7 0x000001203e97 <unknown>
#8 0x000001202970 <unknown>
#9 0x0000033a9313 main
#10 0x7f704c6e1f45 __libc_start_main
#11 0x000000574d79 <unknown>

Aborted (core dumped)

@brice-gros
Copy link
Contributor

@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

@PunchyRascal
Copy link

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.

@mindis
Copy link

mindis commented Mar 1, 2017

same issue here

@olikasg
Copy link

olikasg commented Apr 18, 2017

I ran into the same problem with Win7 and Xming. Later I tried to VcXsrv and it worked with that.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

10 participants