Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!yale!root
From: root@yale.UUCP (Celray Stalk)
Newsgroups: comp.windows.x
Subject: Does xterm -t normally work?
Message-ID: <54940@yale-celray.yale.UUCP>
Date: 27 Mar 89 20:25:54 GMT
References: <34700008@primerd> <8903271533.AA04533@EXPIRE.LCS.MIT.EDU>
Reply-To: galvin-peter@CS.YALE.EDU (Peter Baer Galvin)
Organization: Yale University Computer Science Dept, New Haven CT  06520-2158
Lines: 24

I've tested this on our IBM RTs and Suns now so it's not a system
specific problem... starting xterm with the -t switch causes xterm to
crash with the following error:

% xterm -t
X Protocol error:  not a valid window ID
  Major opcode of failed request:  61 (X_ClearArea)
  Minor opcode of failed request:  0
  Resource id in failed request:  0x0
  Serial number of failed request:  32
  Current serial number in output stream:  40
%

This sounds somewhat familiar so it might already be fixed, but I've been
keeping up with the patches and don't recalling seeing it. Thanks in advance.


					      --Peter

------------------------------------------    --------------------------------
Peter Baer Galvin       		      (203)432-1254
Senior Systems Programmer, Yale Univ. C.S.    galvin-peter@cs.yale.edu
51 Prospect St, P.O.Box 2158, Yale Station    ucbvax!decvax!yale!galvin-peter
New Haven, Ct   06457			      galvin-peter@yalecs.bitnet