#114 Unknown Rectangle Encoding ###### -> exiting

Interface (96)

I am having a problem connecting my OSx to Win
XP home. Frequently I get the following error:

"Unknown rectangle encoding ####### -> exiting"

I am using v2.0b2.

This problem occurs during typing of characters but not
point & click. Sometimes it occurs if the screensaver
(showing my picutres) has come on.

Sometimes this problem makes CotVNC literally unusuable
because of repeated need to reconnect, other times it
happens sporadically.

Any help would be appreciated, but I'd still like to
thank you for all your hard work on this project!


  • Jason Harris

    Jason Harris - 2004-12-08

    Logged In: YES

    This seems to be fixed in CVS for the upcoming Chicken 2.0b3. If you'd
    like to pull from CVS, build and test, that'd be great.

  • Jason Harris

    Jason Harris - 2004-12-08
    • assigned_to: nobody --> smeger
    • status: open --> open-fixed
  • Dave

    Dave - 2004-12-13

    Logged In: YES

    I am also impacted by this bug. When will 2.0b3 be released?
    Alternatively, how do I compile the Mac OS/X version upon downloading
    the cvs source?

  • Jason Weathered

    Jason Weathered - 2005-02-22

    Logged In: YES

    This problem is occuring for me both with 2.0b2 and CVS HEAD
    when trying to connect to a UltraVNC server.

  • Nobody/Anonymous

    Logged In: NO

    I am experiencing the same problem connecting to a VNC server on a Linux
    box. Not fixed as of the current CVS (7 March 2005). FWIW, I have the
    same or similar problem with all VNC viewers I try on MacOS X.


  • Daniel E. Sabath

    Logged In: YES

    Please disregard my previous post (as nobody, 3 March 2005). I solved this
    problem by updating my vnc-server on Fedora Core 3 to version 4.0.8.

  • Jason Harris

    Jason Harris - 2005-08-23

    Logged In: YES

    Resolved for Chicken 2.0b3.

  • Jason Harris

    Jason Harris - 2005-08-23
    • status: open-fixed --> closed-fixed
  • Buzunis

    Buzunis - 2006-01-14

    Logged In: YES

    Using OSx 10.4.4 and CVNC v2.0b3, still same effect as described. Supposedly
    fixed in v2.0b3, but I don't find that. I am connecting to a XP VNC host.


Log in to post a comment.