search

TurboVNC / turbovnc

Main TurboVNC repository
https://TurboVNC.org
GNU General Public License v2.0
761 stars 138 forks source link

"Attempted to configure an invalid screen layout" and "Rect too big" #292

Closed nathanshearer closed 3 years ago

nathanshearer commented 3 years ago

I believe this is an issue with the vncviewer side and not the server side since UltraVNC vncviewer is able to connect successfully, while both TurboVNC and TigerVNC fail with these errors:

VNC Server

VNC Client

https://github.com/TigerVNC/tigervnc/issues/1257

nathanshearer commented 3 years ago

Error log from TurboVNC vncviewer:

$ vncviewer 
libjawt.so path: /etc/java-config-2/current-system-vm/lib/amd64
CConn: connected to host 192.168.0.110 port 5900
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
CConn: Requesting Tight encoding
TurboVNC Helper: Disabling X11 full-screen mode for window 0x07400060
CConn: Enabling GII
No extended input devices.
CMsgHandler: Server sent us an invalid screen layout
CMsgReader: Rect too big: 64x64 at 960,512 exceeds 0x0
Rect too big
dcommander commented 3 years ago

It appears that UltraVNC unfortunately decided to invent their own server-to-client extended desktop size message: https://github.com/ultravnc/UltraVNC/blob/main/rfb/rfbproto.h#L1191-L1232 As near as I can determine, that violates the protocol: https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#extendeddesktopsize-pseudo-encoding

Neustradamus commented 2 years ago

@nathanshearer: Have you tested the last UltraVNC?