Think I've got a bit further with the BadValue 0x20 problem. Here is
a backtrace from the XCreatePixmap function that causes the trouble
('finish' in gdb gives the X error message):
#0 0x0013ed66 in XCreatePixmap () from /usr/X11R6/lib/libX11.so.6
#1 0x0024b2c0 in XcursorImageLoadCursor () from
Just to have all the information in one email, here is what I tried
tonight.
The binaries were built unpacking XFree86-4.3.0.tar.gz over the xc
directory from vnc-4.0b3-unixsrc.tar.gz, and then applying xc.patch
with 'patch -p0 -i xc.patch'. Here is the %build part of the spec
file I used:
%conf
Tristan Richardson said:
> Can you get xdpyinfo to tell you anything
> about
> the visuals and pixmap formats supported by the Xvnc?
My output is identical to the one Tim sent to the list.
> Another thing you
> might try is to run the Xvfb executable which should also have been built
> alongside
Incidentally, if I set my xstartup to run GNOME, I get this error in
the output:
(gnome-session:9690): Gdk-WARNING **: The X server advertises that
RENDER support is present,
but fails to supply the necessary pixmap support. In
other words, it is buggy.
Could that be relevant?
Tim.
*/
[demime
I'm also seeing the BadValue errors when trying to start clients.
Xvfb from the same build tree is fine. Here is the xdpyinfo output
for the Xvnc display:
name of display::3.0
version number:11.0
vendor string:The XFree86 Project, Inc
vendor release number:4030
XFree86 version
alongside Xvnc, and see if it has the same problem. That might provide some
clues.
Cheers
Tristan
- Original Message -
From: "William Hooper" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 8:09 PM
Subject: VNC 4.0b3 and RHL 9
> I
I took some time today, and thanks to Tim Waugh and Dave Love got VNC
4.0b3 to build on my RHL 9 machine. This is using gcc 3.2.2 and XFree86
4.3.0 (sources from the XFree86-4.3.0.tar.gz file included in
XFree86-4.3.0-2.src.rpm from Red Hat).
I've just tested Xvnc using it basically as a replacem
