vncviewer fais vith "Rect too big"

[chantra]

Binary package hint: xvnc4viewer

package: xvnc4viewer 4.1.1+xorg1.0.2-0ubuntu4

how to reproduce:

1. server is run on remote kde desktop using krfb with or without authentication . screen size: 1024x768
2. vncviewer is set to use xvnc4viewer backend though update-alternatives. client screen size 1440x900

Connecting to the server let you see the remote host screen and then crash with

VNC Viewer Free Edition 4.1.1 for X - built Jan 7 2007 17:30:38
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Sun May 27 19:02:43 2007
 CConn: connected to host surya port 5900

Sun May 27 19:02:44 2007
 CConnection: Server supports RFB protocol version 3.3
 CConnection: Using RFB protocol version 3.3

Sun May 27 19:02:47 2007
 TXImage: Using default colormap and visual, TrueColor, depth 24.
 CConn: Using pixel format depth 6 (8bpp) rgb222
 CConn: Using ZRLE encoding

Sun May 27 19:02:48 2007
 CConn: Throughput 1957 kbit/s - changing to full colour
 CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
Rect too big: 2602x45584 at 25104,11138 exceeds 1024x768
 main: Rect too big

[dmoyne (daniel-moyne)]

same problem here :
server : 1024 x 768
client : 1680 x 1050
$ vncviewer 192.168.1.150

VNC Viewer Free Edition 4.1.1 for X - built Apr 16 2008 13:23:14
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Wed Oct 29 23:03:43 2008
 CConn: connected to host 192.168.1.150 port 5900

Wed Oct 29 23:03:45 2008
 CConnection: Server supports RFB protocol version 3.3
 CConnection: Using RFB protocol version 3.3
.....
authorization given for access on server
.....
Wed Oct 29 23:03:45 2008
 CConnection: Server supports RFB protocol version 3.3
 CConnection: Using RFB protocol version 3.3

Wed Oct 29 23:06:04 2008
 TXImage: Using default colormap and visual, TrueColor, depth 24.
 CConn: Using pixel format depth 6 (8bpp) rgb222
 CConn: Using ZRLE encoding
Rect too big: 31349x28192 at 0,0 exceeds 1280x1024
 main: Rect too big

[Jeremy Melanson (jmelanson)]

Had this exact problem on Gutsy, Hardy, and now Intrepid, using "xvncviewer -ZlibLevel 7 [vnc_display]".

Most of the VNC displays I'm connecting to are Windows 2003 running on Xen (SuSE Linux Enterprise Server 10 SP2). The display sizes range from 640x480 to 800x600. I typically access them through SSH port forwarding, but that may be irrelevant.

Anyway, long story short, I moved over to xtightvncviewer (based on the post I found at http://ubuntuforums.org/showthread.php?t=695273 ). The problem completely went away, but the speed of the session was abysmally slow (VNC Displays are at a remote data center, accessed through a VPN tunnel). It turned out I needed to specify the encodings. The command that I'm running now is:
xtightvncviewer -compresslevel 7 -encodings "copyrect tight hextile zlib corre rre raw"
I just put that in my .bash_aliases as the command 'vnc'. So all I need to type is 'vnc [vnc_display]'.

Works like a charm.

[Mike Hicks (hick0088)]

Interesting idea with xtightvncviewer, but I end up getting a similar problem with it too. Here I was connecting to a QEMU session booting OpenSolaris:

    [mhicks@accra][~]$ xtightvncviewer -compresslevel 7 -encodings "copyrect tight hextile zlib corre rre raw" localhost:1
    Connected to RFB server, using protocol version 3.8
    No authentication needed
    Authentication successful
    Desktop name "QEMU"
    VNC server default format:
      32 bits per pixel.
      Least significant byte first in each pixel.
      True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
    Using default colormap which is TrueColor. Pixel format:
      32 bits per pixel.
      Least significant byte first in each pixel.
      True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
    Using shared memory PutImage
    Rect too large: 720x400 at (0, 0)
    ShmCleanup called
    [mhicks@accra][~]$

Well, that's a different package, and I don't want to file bugs for that here.

I seem to have the biggest problems in xvnc4viewer when the emulated system is changing video resolution, which happens multiple times in the process of booting a guest. In QEMU or KVM, the resolution also usually changes when accessing the built-in management console by pressing Ctrl+Alt+2 and then change resolution again to go to the emulated VGA by pressing Ctrl+Alt+1.

One potential problem is that xvnc4viewer seems to destroy and re-create a window whenever the resolution changes (well, my compiz window manager thinks it's doing that anyway -- I'm getting the window open/close effects to trigger at these times). I'm suspicious that there may be a timing issue where the client may be trying to draw an image at the new resolution before the window has switched, or in that instant between the old window being destroyed and the new one being created.

Of course, there's a decent probability that there are bugs in the bulit-in VNC servers on QEMU and KVM, but the client should be more tolerant of bogus data coming down the pipe.

[Gustav Svensson (gustav-svensson)]

VNC Viewer Free Edition 4.1.1 for X - built Apr 16 2008 13:02:40
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Fri Aug 7 00:22:00 2009
 CConn: connected to host 192.168.0.1 port 5900
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 TXImage: Using default colormap and visual, TrueColor, depth 24.
 CConn: Using pixel format depth 6 (8bpp) rgb222
 CConn: Using ZRLE encoding

Fri Aug 7 00:22:01 2009
 CConn: Throughput 20001 kbit/s - changing to hextile encoding
 CConn: Throughput 20001 kbit/s - changing to full colour
 CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
 CConn: Using hextile encoding
Rect too big: 298x1 at 1,6656 exceeds 1024x768
 main: Rect too big

[m1fcj (hakan-koseoglu)]

Remote machine is a kubuntu 8.04 with KDE desktop sharing. KRDC fails too.

hakan@photon:~$ xtightvncviewer -compresslevel 7 -encodings "copyrect tight hextile zlib corre rre raw" remoteserver:0
Connected to RFB server, using protocol version 3.3
Performing standard VNC authentication
Password: libv4lconvert: Error decompressing JPEG: EOF while search for a RST marker.

Authentication successful
Desktop name ""
VNC server default format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap which is TrueColor. Pixel format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Rect too large: 29997x27745 at (0, 0)

[Gustav Svensson (gustav-svensson)]

For some reason, setting FullColor=1 solved the problem for me.

[nerling (nerling)]

FullColor=1 does work for me too.

[Eduardo Habkost (ehabkost)]

This is due to a flaw on the VNC protocol. You can work around it by using the -AutoSelect=0 option. More info at: http://<email address hidden>/msg04879.html

[Clint Byrum (clint-fewbar)]

Since there are no recent reports, can somebody affected please confirm that this is still happening on a supported release of Ubuntu (preferrably 11.10 or the new development release, as this is really not a High priority bug that we would SRU to 10.04).

Marking Incomplete, priority medium.

[Launchpad Janitor (janitor)]

[Expired for vnc4 (Ubuntu) because there has been no activity for 60 days.]

[DiagonalArg (diagonalarg)]

This is happening on ubuntu 12.04 using xtightvncviewer on a local LAN using the command:

vncviewer -via dev@<local-ip> -encodings "hextile" -quality 0 -nocursorshape -geometry 1640x1025 localhost

[DiagonalArg (diagonalarg)]

(That, by the way, is attempting connection to a Mac.)

[reklak (reklak)]

When connecting from Ubuntu 14.0.4 to MacBook, using TightVNC Viewer version 1.3.9, I've got an error:
Rect too large: 1282x1026 at (0, 0)

[XANi (xani666)]

Same error happens when connecting to libvirt's VM VNC console