Arch Linux

amca01

Member

Registered: 2008-12-28

Posts: 61

vncdesk suddenly stops working with XIO: Fatal IO error

I have set up vncdesk to run Matlab at lower screen resolution: Matlab's java interface doesn't play nicely with my high definition screen. This was all working perfectly until just a few hours ago, when my attempts to start vncdesk with

   

vncdesk 2 matlab

produced:

Xvnc TigerVNC 1.7.0 - built Sep  8 2016 19:36:24
Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11804000, The X.Org Foundation

Fri Sep 30 20:29:02 2016
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5902
 vncext:      created VNC server for screen 0

Fri Sep 30 20:29:03 2016
 Connections: accepted: [::1]::51930
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VeNCrypt(19)
 SVeNCrypt:   Client requests security type TLSVnc (258)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":2"
      after 135 requests (135 known processed) with 0 events remaining.
matchbox: can't open display! check your DISPLAY variable.
xterm: Xt error: Can't open display: :2
Disconnected from server

I restarted my X server, which made no difference.  I'm completely stumped by this, I have no idea what's going on, or what's caused it.  I am using the matchbox window manager within vncdesk, which I invoke with "matchbox-window-manager&".  (This also worked fine up until recently).

What did happen a while ago was that vncdesk froze, so I opened up a new virtual terminal, and killed the application.  Maybe it's never properly recovered from that kill?  But I have no idea where it may have left files which have not been properly cleaned up, so to speak.

Anyway, advice would be welcome!

r0b0t

Member

From: /tmp

Registered: 2009-05-24

Posts: 511

Re: vncdesk suddenly stops working with XIO: Fatal IO error

No idea really but if you could try rebooting your host than try again and monitor the end for errors, the connection seems fine (although double check if the security certificates are meet) , and if you have imported and everything is fine next step would be to debug and analyse the end host for problems..