-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is the problem with the viewer or the server?

The Unix viewer prints various information about the server it's connecting to 
and the display it is running on; for example:

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 and visual, TrueColor, depth 24.
Got 256 exact BGR233 colours out of 256
Using BGR233 pixel format:
  8 bits per pixel.
  True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6

Here, the VNC server is running 8 bit TrueColour, which is the default if you 
don't specify anything, and the VNC viewer is connecting to a TrueColour 
display.

With an 8 bit TrueColour display, there are only 3 bits for red and green, and 
2 bits for blue, resulting in a limited palette indeed (only 3 levels of 
gray-scale, for example).

The fix for this is to supply appropriate options to Xvnc; possiblities 
include '-cc 3' (a pseudo-colour display), or '-depth 16' or '-depth 24' (16 
bit or 24 bit TrueColour displays, respectively). The higher depths will 
result in greater network traffic (and slower displays, of course); on the 
other hand, in pseudo-colour the display will have to be redrawn more often 
(due to the way VNC handles pseudo-colour VNC servers).

An alternative problem may be that the local display (where the VNC viewer is 
running) is a pseudo-colour display, and the colourmap is full. In this case, 
the viewer's message will indicate something like:
  Using default colormap and visual, PseudoColor, depth 8
  Got <n> exact BGR233 colours out of 256
where <n> is some small number.

This is because some other local application is hogging the colour map; web 
browsers are often guilty of this.

Here, there are several alternatives:
  * Close the application that is hogging the colour map.
  * Tell the VNC viewer to use a private colour map ('-owncmap')
  * If the local supports multiple depths (as is the case for some Sun Sparc 
hardware), use '-truecolour -owncmap'). PC hardware is unlikely to support 
this, though.
  * Change the local server to TrueColour (16 or 24 bit).

Starting the VNC server as root or as a non-root user is probably not directly 
related to the problem.

On December 13, 2002 06:58 am, Paul A. Cheshire wrote:
> I need to manage about 5 separate desktops for non-root users connecting to
> the above.
>
> Unfortunately, if Xvnc is started by a non-root user strange things happen
> with the colormap and/or color depth. The effect is that the palate
> contains insufficient colours to display applications properly.
>
> If they connect to a desktop presented by an instance of Xvnc started by
> root then all is well.

- -- 

Grant McDorman <[EMAIL PROTECTED]>, Sr. Software Design Consultant
Cedara Software Corp.  <URL:http://www.cedara.com>
  (formerly I.S.G. Technologies Inc.)
Mississauga, Ontario, Canada

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (SunOS)

iD8DBQE9+gESLVa+EmyjizARAhUwAJ0W/3pvgksKKyDFHmMjwq42yikBzwCglsi0
AVMooJTJ6d8rW1MOaqo+IgA=
=nkFP
-----END PGP SIGNATURE-----
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to