Sun crashing with 24-bit and netscape7

[Shing-Fat Fred Ma]

Regarding the following problem that
I posted, I made a typo.  I'm actually using
TightVNC1.2.2, and the log file says
it's using Xvnc version 3.3.3r2,
Protocol version 3.3.  If anyone responds
to my original post (hopefully...), could
you please copy it to the vanilla VNC
mailing list (I've copied them as well).

Thanks.

Fred

Shing-Fat Fred Ma wrote:

>  Hi, I'm using netscape 7 on solaris 8,
> through VNC.  I have to use 24-bit for
> a number of reasons, not the least of
> which is the color flashing that comes
> with private colormaps when applications
> can't allocate enough colors.  But also,
> acroread5.0 for solaris 8 needs either
> 24-bit or the VNC-unfriendly pseudocolor.
>
> This is leading to two problems.
>
> Problem#1
> ----------
> Netscape7 causes the
> 24-bit server to crash, and only when
> I visit the TightVNC mailing list archive.
> Very strange, I see the page for about
> a split second.  The error is:
>
> X connection to malawi:2.0 broken (explicit kill or server shutdown).
> xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server 
> "malawi:2.0"
>
> Here, malawi is the machine name.
>
> Problem#2
> ---------
> If I try to start up the VNC server with
> its default 8-bits so as to avoid this
> website-specific problem, there is a
> conflict with the viewer, which I launch
> from a 24-bit desktop (another VNC server
> running on the same machine).  What
> happens is that the viewer (and the 8-bit
> VNC server to which it tries to connect)
> crashes the moment it is launched.  I get
> the message:
>
> VNC server default format:
>  8 bits per pixel.
>  True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
> Using default colormap which is TrueColor.  Pixel format:
>  32 bits per pixel.
>  Most significant byte first in each pixel.
>  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
> Same machine: preferring raw encoding
> vncviewer: VNC server closed connection
>
> The log file says:
>
> xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server 
> "malawi:2.0"
> X connection to malawi:2.0 broken (explicit kill or server shutdown).
> X connection to malawi:2.0 broken (explicit kill or server shutdown).
> xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server 
> "malawi:2.0"
>
> This happens even if I launch the viewer
> with "-depth 8" (same message and
> log file content).  It does not happen if I
> invoke the viewer from an 8-bit desktop.
>
> Since the message and logfile is the same
> regardless of whether the veiwer is started
> with "-depth 8", I suspect that the the VNC
> server is ignoring this specification (or the
> viewer is ignoring it and not sending it to the
> VNC server).  I don't know if the crashing
> would stop if the 8-bit gets properly received
> and honoured by the VNC server.
>
> I'm using TightVNC1.1.2 (haven't been able
> to compile any more recent versions on Solaris8
> as nonroot).
>
> Thanks for any suggestions.
>
> Fred
>

-- 
Fred Ma, fma@doe.carleton.ca
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6