sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: hc05@summitis.com
To: sam-fans@hawkwind.utcs.toronto.edu (Sam mailing list)
Subject: sam or tk bug?
Date: Wed, 8 Mar 1995 14:12:20 -0500	[thread overview]
Message-ID: <9503081840.AA20542@cheetah> (raw)

>
>I've started using sam on RS 6000's recently and have been getting
>the following error relatively often (3 times in the past two days):
>
>	Xlib:  sequence lost (0x10006 > 0xfcb) in reply type 0x0!
>	X Error of failed request:  0
>	  Major opcode of failed request:  0 ()
>	  Serial number of failed request:  6
>	  Current serial number in output stream:  4043
>
>Then samterm exits.  Has anyone seen this before?

I used to get a lot of X errors like this in sam on the RS/6000, but I
don' anymore.  I never figured out for sure why, but I think getting
X11R5 helped me (we were on X11 R4 for a long time).  In any case, I
can't remember the last time it died on me.  It could be a sam version
issue too.  Unfortunately I don't know how to tell what version I have.  I 
think it is the one before the recent release, with the samx2 patches added
in.

Beirne


-- 
-------------------------------------------------------------------------------
Beirne Konarski                 | Reading maketh a full man, conference a
beirnek@summitis.com            | ready man, and writing an exact man.
"Untouched by Scandal"          |       -- Francis Bacon
-------------------------------------------------------------------------------



             reply	other threads:[~1995-03-08 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-03-08 19:12 hc05 [this message]
1995-03-09  0:50 ` Michael F. Ledwidge
  -- strict thread matches above, loose matches on Subject: below --
1995-03-08 17:30 Castor Fu
1995-03-08 18:21 ` DaviD W. Sanderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9503081840.AA20542@cheetah \
    --to=hc05@summitis.com \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).