Re: randomly dying xterms
Re: randomly dying xterms
- Subject: Re: randomly dying xterms
- From: "Chris Linstid" <email@hidden>
- Date: Sat, 1 Nov 2008 12:32:19 -0400
A bit more information for my situation. I had been setting TERM to
xterm-color when I was having the xterms dying in the manner I listed.
I switched TERM to xterm and it has now stopped. I wonder if there's
something screwy with the termcap info for xterm-color... either on
the box I'm ssh'ing to or my Mac.
Also have a correction for step 2, I'm actually ssh'ing to a FreeBSD
system, not a linux system.
- Chris
On Thu, Oct 30, 2008 at 4:18 PM, Chris Linstid <email@hidden> wrote:
> I've seen this as well, but for me it's very specific.
>
> 1. Open xterm
> 2. ssh to my linux box, run screen with irssi
> 3. Minimize xterm
> 4. Go to another application, switch between other apps and X11. This
> part takes some time and I haven't been able to figure out if anything
> I'm doing during that time is causing this.
> 5. Restore xterm - at this point, the xterm goes away and I get this
> in the console:
>
> Oct 30 16:12:29 clinstid-mac1 [0x0-0xbb0bb].org.x.X11[2002]: Xlib:
> sequence lost (0x10000 > 0x9c9) in reply type 0x0!
> Oct 30 16:12:29 clinstid-mac1 [0x0-0xbb0bb].org.x.X11[2002]: xterm:
> warning, error event received:
> Oct 30 16:12:29 clinstid-mac1 [0x0-0xbb0bb].org.x.X11[2002]: X Error
> of failed request: BadRequest (invalid request code or no such
> operation)
> Oct 30 16:12:29 clinstid-mac1 [0x0-0xbb0bb].org.x.X11[2002]: Major
> opcode of failed request: 0 ()
> Oct 30 16:12:29 clinstid-mac1 [0x0-0xbb0bb].org.x.X11[2002]: Serial
> number of failed request: 0
> Oct 30 16:12:29 clinstid-mac1 [0x0-0xbb0bb].org.x.X11[2002]: Current
> serial number in output stream: 2505
>
> OS X 10.5.5
> XQuartz 2.3.1 (xorg-server 1.4.2-apple17)
>
> - Chris
>
>
>
> On Fri, Oct 24, 2008 at 5:52 PM, Ronald Cohen <email@hidden> wrote:
>> With the latest X11 (2.3.1) and Mac OS X 10.5.5, I seem to find xterms
>> randomly dying. Not frequently, but seemingly about once a day.
>> Whatever process was running in that xterm (which can be almost anything) is
>> killed at the same time. It is not confined to xterms, but seemingly any
>> xwindow; I've also had the experience with xemacs. X11 itself usually
>> stays alive (though I've had less frequent crashes of X11 as well).
>>
>> I'm not sure if I'm seeing something useful here, but I do notice, at about
>> the right time in the console log, the following:
>>
>>
>> 10/24/08 2:26:01 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x12020 > 0x389a) in reply type 0x20!
>> 10/24/08 2:26:01 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x1206f > 0x389a) in reply type 0x20!
>> 10/24/08 2:26:01 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x16568 > 0x389a) in reply type 0x20!
>> 10/24/08 2:34:05 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x12020 > 0x389a) in reply type 0x20!
>> 10/24/08 2:34:05 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x16570 > 0x389a) in reply type 0xa!
>> 10/24/08 2:34:05 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x12074 > 0x389a) in reply type 0x20!
>> 10/24/08 2:34:15 PM [0x0-0xad0ad].org.x.X11[4134] Xlib: sequence lost
>> (0x10000 > 0x389a) in reply type 0x20!
>>
>> I think these may just be the result of my attempt to make this window
>> active by selecting the window from the "window" menu in X11. I don't see
>> anything else terribly relevant. Nothing for example in a crash log.
>>
>> Anyone else having such experiences, or ideas?
>>
>> Thanks,
>>
>> Ron Cohen
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> X11-users mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden