Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!ames!winken!lll-crg.llnl.gov!hbrand
From: hbrand@lll-crg.llnl.gov (Hal Brand)
Newsgroups: comp.unix.ultrix
Subject: UWS V2.0 Xqdsg server problems
Summary: Xlib sequence lost messages and failures with CLX
Keywords: X Xqdsg CLX Xlib
Message-ID: <25143@winken.LLNL.GOV>
Date: 12 May 89 21:35:20 GMT
Sender: usenet@winken.LLNL.GOV
Reply-To: hbrand@lll-crg.llnl.gov.UUCP (Hal Brand)
Distribution: usa
Organization: Lawrence Livermore National Laboratory
Lines: 36

I am having the following problems with my DECWindows server under UWS V2.0
on my color VS2000:

1) I get "Xlib: Sequence lost" error messages. Mostly when running GNU Emacs
   and I get them when running local, with a SUN 3/260 (SUNOS V4) as
   the client machine, and with a VAX 11/785 (4.3 BSD) as the client!
   After about 3 of these messages, emacs freezes and must be "kill"ed!

2) CLX (Franz Allegro CL with CLX/XCW) running on the Sun 3/260 consistantly
   gives a sequence lost message. Interestingly, it expected 7 and got 1792.
   Since 7*256 is 1792, I suspect that there may be a "big-endian" (which
   CLX wants) and "little-endian" (which is native to the VS2000) problem!
   The problem occurs on X protocol opcode QueryFont (47) and is consistant!
   The first few bytes of the reply by the VS2000 server as recieved by
   CLX (as best I can tell) are:
   1 0 7 0 0 0 2 215 255 255 0 1 0 6 255 255 255 250 0 0 0 0 0 0 0 3 0 7 0 6.

3) Using XGetImage followed by XPutImage works fine with ZPixmap, but draws
   garbage using XYPixmap (although the garbage is strongly related to the
   original image!)! In a related problem, "xwd -xy | xpr -device ps" produces
   a postscript file that prints garbage very similar to the garbage produced
   when using XYPixmap format. Also, using XCopyArea from the root window
   including subwindows to a pixmap and then using XCopyArea to copy that
   pixmap to a window (i.e. xsnap) produces garbage (but again, garbage
   related to the starting contents)!

4) Many of the cursors (including the upper-left, lower-left, upper-right
   and lower-right brackets) have "dirt" (i.e. random bits set) at the
   bottom of the cursor area!

Does anyone have any information to share about these problems?? I am
especially interested in fixing the sequence lost problem with CLX since
it is preventing work from my VS2000!!!

						Hal Brand
						hbrand@lll-crg.llnl.gov