#44 Incompatible with RealVNC 4.0beta

[Anonymous]

I tried using the Windows beta4 thats available from
www.realvns.com because I have two monitors on my
2000 box at work.

When I connect from home on my eMac running
OSX10.2.8 (through a DigiTunnel), I get the full-screen
just fine, and all mouse activity, screen work, etc work
just fine.

Typing any single key into any other window results in
Chicken crashing - it appears that an unexpected
encoding scheme is being detected.

Typing into a CONSOLE window works fine, which is
odd, but I assume that VNC handles console windows
differently somehow

jeffl@spatialinfo.com

[Jason Harris]

Logged In: YES
user_id=351330

Chicken should be generating a crashlog when it dies. You can get
it by opening /Applications/Utilities/Console or by looking in ~/
Library/Logs/CrashReporter.

It would be helpful if you could attach that here.

[Wout Mertens]

Logged In: YES
user_id=238228

I see the same thing. Details:
type almost any key => You get a window saying "Unknown rectangle
encoding 3145734 -> exiting"

So it doesn't crash, it just stops displaying. Disabling ZRLE makes it
behave normally.

[Nobody/Anonymous]

Logged In: NO

Yes i have the exact same problem, But i like the beta 4 because it
is easy to setup the different servers using different ports. but
when i am on my mac on a remote desktop i obeserve the same
error i cannot use my keyboard!

[Jason Harris]

Logged In: YES
user_id=351330

Okay, sounds like this is the same bug as #688352, which I officially
vote "the worst bug in Chicken".

[Nobody/Anonymous]

Logged In: NO

I submitted the bug originally and I can confirm that in 1.3.6:
a) switching to 24-bit color fixes the problem but my screen ends
up very blue - not a workable alternative
b) switching *off* ZRLE encoding whilst leaving the others seems
to fix the problem, although I haven't tried it heavily - but it "felt
slower"

In no case has it actually *crashed* so there's been no console log
to attach.

jeffl@spatialinfo.com

[Dave Hill]

Logged In: YES
user_id=8211

I've been bashing my head against this for an hour or so. I'm connecting
to vnc server 4.0b4 (Xvnc version 4.0b4 - built Sep 19 2003 09:32:30)
on RH9 from my mac using an SSH tunnel.

Switching the local colour model from 24 bits to 16 bits fixes it, turning
off the encodings didn't help.

I d/l'ed the GEN_2_GUI version from CVS and built it and that fails the
same way.

Dave Hill

[Dave Hill]

Logged In: YES
user_id=8211

Sigh, even that didn't work. I managed to get past the GDM login screen
and open a terminal window, then it died when I tried to type into the
shell.

I have also tried adding "-Protocol3.3" to the Xvnc command line and
that didn't fix it either.

So I'm stuck.

Dave

[Dave Hill]

Logged In: YES
user_id=8211

Me again - success!! Having tried all the other OSX vnc clients
I could find on the net and they all failed the same way, I
got suspicious of the server. If you type "Xvnc 4.0b4 rectangle"
into Google, you get

http://www.realvnc.com/pipermail/vnc-list/2003-November/041754.html

which says "yes, we know there are rectangle problems in 4.0b4!"

To cut a long story short, I found that the Fedora Core 2 RPM
4.0-1.beta4.11 works fine (so far, touch wood), so someone
must have patched it. I was using 4.0-0.beta4.3 before.

Sorry for the previous mutterings, we now return you to your
normal chickens...

Dave Hill

[Jason Harris]

Logged In: YES
user_id=351330

Thanks for the update Dave, it would have sucked to have been banging
on this one for no reason. I appreciate it.

Closing bug.