VcXsrv Windows X Server / Bugs / #137 VcXsrv dies after launch

Darrek - 2021-02-03

Try running

netstat -an | find "6000"

after starting and before it dies to see if it is actually listening on port 6000 like it is supposed to. Also make sure your firewall isn't blocking it.

Also, what is your full command-line?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Hari Prasanna - 2021-02-12
  
  This is what i get on netstat -an | find "6000"
  
  TCP 0.0.0.0:6000 0.0.0.0:0 LISTENING TCP 127.0.0.1:6000 0.0.0.0:0 LISTENING TCP 127.0.0.1:6000 127.0.0.1:58775 ESTABLISHED TCP 127.0.0.1:6000 127.0.0.1:58776 ESTABLISHED TCP 127.0.0.1:58775 127.0.0.1:6000 ESTABLISHED TCP 127.0.0.1:58776 127.0.0.1:6000 ESTABLISHED TCP [::]:6000 [::]:0 LISTENING
  
  Fiirewall doesn't block it . Still i have the same problem.
  
  I launch the VcXsv via the Gui in multiwindow mode with disable access control
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

This is what i get on netstat -an | find "6000"

  TCP    0.0.0.0:6000           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:6000         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:6000         127.0.0.1:58775        ESTABLISHED
  TCP    127.0.0.1:6000         127.0.0.1:58776        ESTABLISHED
  TCP    127.0.0.1:58775        127.0.0.1:6000         ESTABLISHED
  TCP    127.0.0.1:58776        127.0.0.1:6000         ESTABLISHED
  TCP    [::]:6000              [::]:0                 LISTENING

Fiirewall doesn't block it . Still i have the same problem.

Darrek - 2021-02-18

IDK. Looks like it is listening on 6000 as it should and made connections to itself.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Stephen Wall - 2021-02-18
  
  Have you tried launching it using a different disaply number? ':1' perhaps...
  
  From: Darrek darrek@users.sourceforge.net
  Sent: Wednesday, February 17, 2021 7:20 PM
  To: [vcxsrv:bugs] 137@bugs.vcxsrv.p.re.sourceforge.net
  Subject: [vcxsrv:bugs] #137 VcXsrv dies after launch
  
  IDK. Looks like it is listening on 6000 as it should and made connections to itself.
  
  [bugs:#137]https://sourceforge.net/p/vcxsrv/bugs/137/ VcXsrv dies after launch
  
  Status: open
  Group: v1.0_(example)
  Created: Fri Jan 29, 2021 11:49 AM UTC by Hari Prasanna
  Last Updated: Fri Feb 12, 2021 09:19 AM UTC
  Owner: nobody
  
  Hello All,
  
  I freshy installed VcXsrv and tried launching it in multiwindow mode with disable access control box checked. The issue is that VcXsrv dies within a minute after launch. I tried diasbling the firewall as suggested in another ticket. That was in vain. I tried digging deeper and found the log file - the contents are as below. None of the other suggestions found online seemed to work for me.
  
  Does anyone know how to fix this? I am stuck with resolving this since almost a week. Thanks!
  
  Welcome to the VcXsrv X Server
  Vendor: The VcXsrv Project
  Release: 1.20.9.0
  
  OS: Windows NT 6.2 build 9200 (64-bit)
  Contact: marha@users.sourceforge.net
  
  LoadPreferences: C:\Users\hprabakaran\AppData\Roaming.XWinrc not found
  LoadPreferences: Loading C:\Program Files\VcXsrv\system.XWinrc
  (II) AIGLX: Testing pixelFormatIndex 5
  (II) GLX: enabled GLX_SGI_make_current_read
  (II) GLX: enabled GLX_SGI_swap_control
  (II) GLX: enabled GLX_MESA_swap_control
  (II) GLX: enabled GLX_SGIX_pbuffer
  (II) GLX: enabled GLX_ARB_multisample
  (II) GLX: enabled GLX_SGIS_multisample
  (II) GLX: enabled GLX_ARB_fbconfig_float
  (II) GLX: enabled GLX_EXT_fbconfig_packed_float
  (II) GLX: enabled GLX_ARB_create_context
  (II) GLX: enabled GLX_ARB_create_context_profile
  (II) GLX: enabled GLX_ARB_create_context_robustness
  (II) GLX: enabled GLX_EXT_create_context_es2_profile
  (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  (II) 1172 pixel formats reported by wglGetPixelFormatAttribivARB
  (II) GLX: Initialized Win32 native WGL GL provider for screen 0
  winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
  winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
  winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
  winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
  winMultiWindowXMsgProc - Could not open display, try: 3, sleeping: 5
  winInitMultiWindowWM - Could not open display, try: 3, sleeping: 5
  winInitMultiWindowWM - Could not open display, try: 4, sleeping: 5
  winMultiWindowXMsgProc - Could not open display, try: 4, sleeping: 5
  winInitMultiWindowWM - Could not open display, try: 5, sleeping: 5
  winMultiWindowXMsgProc - Could not open display, try: 5, sleeping: 5
  winInitMultiWindowWM - Failed opening the display. Exiting.
  (EE) Server terminated with error (1). Closing log file.
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/vcxsrv/bugs/137/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Bugs: #137
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Hari Prasanna - 2021-02-19
    
    Well, that seemed to do the trick. Thank you. But why do you think it does not work with display number 0?
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Darrek - 2021-02-20
      
      Try running netstat with VcXSrv not running. Maybe something else is already listening on port 6000...
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Hari Prasanna - 2021-02-22
        
        TCP 127.0.0.1:6000 0.0.0.0:0 LISTENING
        
        This is the output of netstat when VcXsrv is not running
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Darrek - 2021-02-23
        
        That means something else is already using port 6000 which is the default port for display 0.
        
        netstat -abn will help you identify the program already on that port.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

VcXsrv dies after launch

Group

Searches

Help

#137 VcXsrv dies after launch

Related

Discussion

Related