BUG: vncserver changes bits-per-pixel to 0 after disconnect

[Jeff Stearns]

I'm encountering a painful problem with vncserver 3.3.3r1 running on an x86
using Red Hat Linux 6.1.  If the client disconnects abruptly, the server
becomes so confused that it can't handle any further connections.

Under normal conditions, the server comes up fine, and my Windows-based
client connects happily.  And things continue to work fine, so long as I am
careful to quit the client cleanly each time.

The problem happens after a client disconnects abruptly (if, for example,
the network cable is unplugged or the client machine crashes).  This leaves
the server in a state that thwarts further connections.  Once the server is
confused, any client that attempts to open a connection to the server will
die shortly after the password exchange.

I took a close look at the log files and I note that after an abrupt
disconnect, the server decides that bits-per-pixel is now zero.  This
completely confuses any vnc client that tries to connect:
    - a Windows client will an ungraceful death after the password
      exchange without even pausing to post an error dialog.
    - an X-based Linux client will also die ungracefully, leaving behind
      a little bit of log file mentioning that bits-per-pixel is zero.

The bug is completely repeatable on my office network.

Does anybody have any suggestions for diagnosing and fixing this problem?

Thanks!

Jeff Stearns / jeffstearns "at" home.com / 510-649-1816 / cell: 510-326-8557
---------------------------------------------------------------------
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
---------------------------------------------------------------------