![]() TcpSocket: Connecting to arrakis port 5900ĬConn: connected to host arrakis port 5900ĬConnection: Server supports RFB protocol version 3.8ĬConnection: Using RFB protocol version 3. The initial connection, prior to entering fullscreen mode (in the simplest case here, doing away with SSH tunnelling and the like for the sake of simplicity) is:Ĭopyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)ĭecodeManager: Creating 4 decoder thread(s) The machine running vncviewer is running xorg-server 1.20.0 and Mesa 18.1.1 (Intel graphics) I'm not sure what other bits of software version info might help. I have verified that two other VNC clients can connect to the x11vnc instance just fine, so I don't think that the problem is on x11vnc's side. Unfortunately I don't use vncviewer too often, so I don't have a tighter timeline than that, or what update in particular might have caused the issue. This has been working fine for many years now, so some recentish update on my system (within the last three months or so) triggered this. VNC Viewer Plus 1.2.11 l phn mm kim sot my tnh t xa vi tnh nng v cng mnh m dnh ring cho cc my tnh c b vi x l Intel. At that point I have to hop out to a text console or SSH in remotely to kill the vncviewer process, which gives me control of the X session again. ![]() ![]() It works fine until I go into fullscreen mode, at which time I just get a blank grey screen which seems impervious to input. Hello - I'm having problems with tigervnc-1.8.0's vncviewer, when connecting to an x11vnc instance on another machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |