Repeat question: why does Windows VNC client die immediately on startup

[Brandon Ibach]

Quoting Ronald L Fox <rfox "at" dls.queens.org>:
> Perhaps someone can explain how to keep vncserver from getting into this
> state.
> The other thing that appears in all of my logs when this occurs is:
> 
>  rfbSetTranslateFunction: server bits per pixel not 8, 16 or 32
> 
   This second message is simply a result of the function in the
server which sets up the pixel format actually checking the validity
of the format, which it does *after* printing it.
   From a quick look at the code, it would seem that it is the viewers
which are actually "requesting" zero bits per pixel.  So, the trick is
to figure out why the viewer might be doing that.  Is this situation
totally reproducible?  Can you run a debugger on it?  Which viewer is
it, again (I forget, and I'm too lazy to go back and check right now)?

   Guess it's about time to get VNC development a little more
organized, eh folks? :)  I sent an email to the email address for the
VNC team at ORL, suggesting that some moves be made to get some sort
of "development community" going for VNC, but I haven't heard back
from them (and it has been several weeks).
   So, what say ye, AT&T folks?  Shall I repost my message here for
your consideration?

-Brandon :)

---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------