On Mon, 13 Dec 2004 09:15:13 -0600 (CST)
fredb@immanent.net (Frederick Bruckman) wrote:

> Perhaps we could make this just a warning?
Don't know. I have no clue about X11, I am a kernel hacker.

> Index: xfree/xc/lib/X11/OpenDis.c
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> RCS file: /cvsroot/xsrc/xfree/xc/lib/X11/OpenDis.c,v
> retrieving revision 1.1.1.5
> diff -u -r1.1.1.5 OpenDis.c
> --- xfree/xc/lib/X11/OpenDis.c	5 Mar 2004 14:24:08 -0000	1.1.1.5
> +++ xfree/xc/lib/X11/OpenDis.c	13 Dec 2004 15:03:15 -0000
> @@ -582,8 +582,10 @@
>  	    fprintf(stderr, "Xlib: Did not parse entire setup message: "
>  	                    "parsed: %ld, message: %ld\n",
>  		    usedbytes, setuplength);
> +#if 0 /* Non-fatal ??? */
>  	    OutOfMemory(dpy, setup);
>  	    return(NULL);
> +#endif
>  	}
> =20
>  /*
This did it:
[jkunz@Zimbo jkunz]$ xclock -update 1=20
Xlib: Did not parse entire setup message: parsed: 848, message: 1600
Fontconfig error: Cannot load default config file
Xlib:  extension "RENDER" missing on display "MrPomeroy:0.0".

And now I have xclock(1) on my screen. xterm(1) works too, but gvim(1)
does not. I started top(1) inside the xterm. This worked for some time
but then, when switching back to the virtual desktop with the xterm, the
xterm was blank and didn't react to any input.

[jkunz@Zimbo jkunz]$ gvim tmp.txt                  =20
Xlib: Did not parse entire setup message: parsed: 848, message: 1600
XIO:  fatal IO error 60 (Connection timed out) on X server
"MrPomeroy:0.0"
      after 45 requests (39 known processed) with 0 events remaining.

> In any case, would you please file a problem report (with NetBSD)?
I'll do so in a few minutes.
--=20


tsch=FC=DF,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/