Bug 390011

Created attachment 214935 [details]
xvnc-problem.png

Screenshot of a vncviewer which shows the broken behaviour.

The depth of my X-server is 24:

mfabian@magellan:~$ xdpyinfo | grep depth
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
  depths (7):    24, 1, 4, 8, 15, 16, 32
  depth of root window:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
    depth:    24 planes
mfabian@magellan:~$ 

I start Xvnc like this:

mfabian@magellan:~$ Xvnc -depth 24 :2 &
14/05/2008 00:37:37 Xvnc version X.org/xf4vnc custom version
14/05/2008 00:37:37 Copyright (C) 2001-2004 Alan Hourihane.
14/05/2008 00:37:37 Copyright (C) 2000-2004 Constantin Kaplinsky
14/05/2008 00:37:37 Copyright (C) 1999 AT&T Laboratories Cambridge
14/05/2008 00:37:37 All Rights Reserved.
14/05/2008 00:37:37 See http://www.tightvnc.com/ for information on TightVNC
14/05/2008 00:37:37 See http://xf4vnc.sf.net for xf4vnc-specific information
14/05/2008 00:37:37 Desktop name 'x11' (magellan:2)
14/05/2008 00:37:37 Protocol versions supported: 3.7, 3.3
14/05/2008 00:37:37 RGB format 8 8 8
14/05/2008 00:37:37 Listening for VNC connections on TCP port 5902
[1] 7214
mfabian@magellan:~$ Could not init font path element /usr/share/fonts/TTF/, removing from list!
Could not init font path element /usr/share/fonts/OTF, removing from list!
14/05/2008 00:37:53 
14/05/2008 00:37:53 Got VNC connection from client 127.0.0.1
14/05/2008 00:37:53 Using protocol version 3.7
14/05/2008 00:37:53 Enabling TightVNC protocol extensions
14/05/2008 00:37:53 Pixel format for client 127.0.0.1:
14/05/2008 00:37:53   32 bpp, depth 24, little endian
14/05/2008 00:37:53   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
14/05/2008 00:37:53   no translation needed
14/05/2008 00:37:53 Using raw encoding for client 127.0.0.1
14/05/2008 00:37:53 Using copyrect encoding for client 127.0.0.1
14/05/2008 00:37:53 Using compression level 1 for client 127.0.0.1
14/05/2008 00:37:53 Using image quality level 6 for client 127.0.0.1
14/05/2008 00:37:53 Enabling X-style cursor updates for client 127.0.0.1
14/05/2008 00:37:53 Enabling cursor position updates for client 127.0.0.1
14/05/2008 00:37:53 Enabling LastRect protocol extension for client 127.0.0.1
14/05/2008 00:37:53 rfbProcessClientNormalMessage: ignoring unknown encoding -223

and the viewer was started like this:


mfabian@magellan:~$ vncviewer -passwd ~/.vnc/passwd :2
Connected to RFB server, using protocol version 3.7
Enabling TightVNC protocol extensions
No authentication needed
Desktop name "mfabian's x11 desktop (magellan:2)"
VNC server default format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.
  Least 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

If use “-depth 16”, i.e.

    Xvnc -depth 16 :2 &
    vncviewer -passwd ~/.vnc/passwd :2

it works without problem.

The script /usr/bin/vncserver seems to use “-depth 24” by
default on my machine, i.e. I always run into this problem
when using

    vncserver :2

If use “-depth 32”, i.e.

    Xvnc -depth 32 :2 &

The Xvnc process starts using all available CPU time immediately and
the viewer started as 

    vncviewer -passwd ~/.vnc/passwd :2

cannot connect.

Only “killall -9 Xvnc” will kill the Xvnc started with “-depth 32”,
“killall Xvnc” is not enough.

Looks like I broke it with this change:

-------------------------------------------------------------------
Mon May  5 14:56:01 CEST 2008 - sndirsch@suse.de

- xorg-server-1.4-vnc-disable_render.diff
  * disabled RENDER support in Xvnc (bnc #385677) 

Yes, it works again if the patch mentioned in comment #7 is removed.

I don't think this a low hanging fruit - both issues. I suggest to change default depth of Xvnc in /usr/bin/vncserver to 16 and keep this bugreport open. 

Well, I don't think that Reinhard will accept this patch. It would be a regression.

--- vncserver.orig      2008-05-14 17:44:42.000000000 +0200
+++ vncserver   2008-05-14 17:57:35.000000000 +0200
@@ -34,7 +34,7 @@
 #
 
 $geometry = "1024x768";
-$depth = 24;
+$depth = 16;
 $desktopName = "X";
 $vncClasses = "/usr/share/vnc/classes";
 $vncUserDir = "$ENV{HOME}/.vnc";
@@ -90,7 +90,7 @@
 
 # Uncomment this line if you want default geometry, depth and pixelformat
 # to match the current X display:
-&GetXDisplayDefaults();
+#&GetXDisplayDefaults();
 
 if ($opt{'-geometry'}) {
     $geometry = $opt{'-geometry'};

xorg-x11-server.changes:
-------------------------------------------------------------------
Wed May 14 18:19:15 CEST 2008 - sndirsch@suse.de

- disabled patch to disable RENDER support in Xvnc, since it broke
  24bit color depth support (bnc #390011)

So I reopened Bug #