vnc-list-digest V1 #805

Jeff Stearns jeffstearns "at" home.com
Tue, 01 Aug 2000 08:10:01 +0000


Steve -

This happens on occasion to the folks in our office.  We use Win98 clients
with RH6.1 and 6.2 servers.

I tend to think that the problem actually happens during the disconnect,
since it seems more likely to occur after a client disconnected uncleanly.
(Hmmm ... maybe it's a SIGPIPE thing...)  But it's all speculation on my
part.  I used to be able to provoke it quite often, but it's become less
likely to happen now that I take more care during disconnect.

I'd also like to hear from anybody who thinks that they might have a lead on
what's going wrong.

Jeff Stearns / jeffstearns "at" home.com / 510-649-1816 / cell: 510-326-8557


> Date: Mon, 31 Jul 2000 13:08:04 -0500
> From: Steve Schicht <sschicht "at" gigasemi.com>
> Subject: VNC Viewer for WinNT4.0 crashes when connecting to RedHat6.0 VNC
> Server  - 0 bpp?
> 
> Hello,
> I thought I'd give this a try one more time :)!
> Does anyone know what 0 bpp means in the log file for the
> unsuccessful connection below?
> 
> I'm including parts of my log file for one successful connection
> and one unsuccessful connection.
> 
> Successful connection:
> 
> 27/07/00 15:48:47 Got connection from client 192.168.1.32
> 27/07/00 15:48:47 Protocol version 3.3
> 27/07/00 15:48:52 Pixel format for client 192.168.1.32:
> 27/07/00 15:48:52   8 bpp, depth 8
> 27/07/00 15:48:52   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
> 27/07/00 15:48:52 no translation needed
> 27/07/00 15:48:52 Using hextile encoding for client 192.168.1.32
> 27/07/00 15:48:52 rfbProcessClientNormalMessage: ignoring unknown encoding
> type 3
> 
> Unsuccessful connection:
> 
> 31/07/00 13:03:16 Got connection from client 192.168.1.32
> 31/07/00 13:03:16 Protocol version 3.3
> 31/07/00 13:03:20 Pixel format for client 192.168.1.32:
> 31/07/00 13:03:20   0 bpp, depth 8, little endian
> 31/07/00 13:03:20   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
> 31/07/00 13:03:20 rfbSetTranslateFunction: server bits per pixel not 8, 16 or
> 32
> 31/07/00 13:03:20 Client 192.168.1.32 gone
> 31/07/00 13:03:20 Statistics:
> 31/07/00 13:03:20   framebuffer updates 0, rectangles 0, bytes 0
> 
> The situation...
> - - latest vncserver on RH6.0 intel machine
> - - latest vncviewer on WinNT4.0 machine
> - - first viewer connection after starting server works fine
> - - _sometimes_ second viewer connection cause the viewer to die
> - terminate a working viewer and then start it a day later
> - viewer puts up machine connection dialog
> - viewer puts up passwd dialog
> - viewer puts up window with black pixels...for a split second
> - viewer silently dies
> - - Once this behavior starts, all connections attemps fail until server
> restart
> 
> I recall finding a message with a search that suggested this could happen if
> vncserver was started in the .vnc directory. Yes, that fixed the problem
> for several people. But currently, the "viewer of death" happens on and off
> for a no known reason.
> 
> I really need to debug this thing and need some suggestions on how to debug
> it.
> 
> thanks in advance,
> 
> Steve
---------------------------------------------------------------------
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
---------------------------------------------------------------------