🚀 go-pugleaf

	I would like to follow up on the recent discusions concerning
problems running xnews vs. MIT and general bugs with xnews, by asking
about any known problems running Motif apps and/or mwm under xnews.

(1)	I for one can almost always get the server to crash with the 
following type messages


XNeWS:  internal error detected (SIGSEGV).
	Report this problem to a knowledgeable person.
Console:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
/usr/openwin/bin/xinit:  connection to X server lost.

OR

XNeWS:  internal error detected (SIGSEGV).
	Report this problem to a knowledgeable person.
/usr/openwin/bin/xinit:  connection to X server lost.
Console:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"

	this always happens when I have a soft link to the mwm binary,
something such as:	mwm -> mwm.1.1.1

	but never when the actual binary is found directly.

(2)	We did at one point have the xnews server, but not the MIT server,
give BadAlloc errors on an eventual call to XCreateWindow, it ended up
being a bogus value for the width parameter but the MIT server didn't
complain. I know that doesn't mean that the MIT server was correct just that
it didn't complain.

(3)	We are occasionally seeing some expose events being lost on
our maps, we never see this happen under the MIT server. I was wondering
whether or not someone else has seen this behaviour?

(4)	and last, xdpyinfo from the OpenWindows release under xnews says
that the server does both Backing Store and Save Unders, is this true?
and if so can anyone show me a piece of code using the Motif widget set
that proves this?


Ramon Santiago				e-mail:	santiago@fgssu1.sinet.slb.com
Finder Graphics Systems			phone:	(415) 927-0100
A Schlumberger Company			fax:	(415) 927-2923
Corte Madera, CA