RE: Weird emacs behavior

RE: Weird emacs behavior

[Leo Chang]

[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]

 

 

  _____  

From: Leo Chang [mailto:lchang@clickshift.com] 
Sent: Monday, January 30, 2006 10:38 PM
To: 'help-gnu-emacs@gnu.org'; 'bug-gnu-emacs@gun.org'
Subject: Weird emacs behavior

 

There is an unexplained behavior that we've seen on a few machines we have
with emacs.  These are Redhat Enterprise Linux boxes that we usually ssh to.
Xforwarding works fine.  All X apps including emacs work fine.  Then, after
a long time (weeks or months), emacs stops appearing in its own window when
you ssh into the box.  Instead, after a long wait, it croaks with something
like "Connection Lost to Xserver. localhost 10:0."  

 

At this point, you can open ALL X applications except for emacs.  Xeyes,
xclock, xterm, firefox all work!  But not emacs.  "emacs -nw" does work, and
emacs in its own Xwindow works if you're directly on the machine.  However,
emacs will not open without the -nw option thru ssh.  (Even though it did
while the machine was running for quite some time.)  Restarting the machine
fixes the problem.


Has anyone ever seen this behavior?  The emacs version is 21.3.1.

 

Any help would be greatly appreciated.


[-- Attachment #1.2: Type: text/html, Size: 4649 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs

Re: Weird emacs behavior

[Ehud Karni]

 [ resent, there was a mistake in the mailing list name ]

On Mon, 30 Jan 2006 22:38:16 -0800, Leo Chang wrote:
>
> There is an unexplained behavior that we've seen on a few machines we have
> with emacs.  These are Redhat Enterprise Linux boxes that we usually ssh to.
> Xforwarding works fine.  All X apps including emacs work fine.  Then, after
> a long time (weeks or months), emacs stops appearing in its own window when
> you ssh into the box.  Instead, after a long wait, it croaks with something
> like "Connection Lost to Xserver. localhost 10:0."
>
> At this point, you can open ALL X applications except for emacs.  Xeyes,
> xclock, xterm, firefox all work!  But not emacs.  "emacs -nw" does work, and
> emacs in its own Xwindow works if you're directly on the machine.  However,
> emacs will not open without the -nw option thru ssh.  (Even though it did
> while the machine was running for quite some time.)  Restarting the machine
> fixes the problem.

Can you do "netstat -a" (look for listening ports in the 6000-6100 range)
when the problem occurs ?
Also, do "echo $DISPLAY".

Try to run "naked" emacs - emacs -q , what happens ?

Ehud.


--
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 GnuPG: 98EA398D <http://www.keyserver.net/>    Better Safe Than Sorry

RE: Weird emacs behavior

[Leo Chang]

Weirdly enough, this behavior went away when I tried it this morning (after
a couple of days).  Emacs is working again.  I can't explain it at all.

-----Original Message-----
From: Ehud Karni [mailto:ehud@unix.mvs.co.il] 
Sent: Wednesday, February 01, 2006 7:46 AM
To: lchang@clickshift.com
Cc: help-gnu-emacs@gnu.org; bug-gnu-emacs@gnu.org
Subject: Re: Weird emacs behavior

 [ resent, there was a mistake in the mailing list name ]

On Mon, 30 Jan 2006 22:38:16 -0800, Leo Chang wrote:
>
> There is an unexplained behavior that we've seen on a few machines we have
> with emacs.  These are Redhat Enterprise Linux boxes that we usually ssh
to.
> Xforwarding works fine.  All X apps including emacs work fine.  Then,
after
> a long time (weeks or months), emacs stops appearing in its own window
when
> you ssh into the box.  Instead, after a long wait, it croaks with
something
> like "Connection Lost to Xserver. localhost 10:0."
>
> At this point, you can open ALL X applications except for emacs.  Xeyes,
> xclock, xterm, firefox all work!  But not emacs.  "emacs -nw" does work,
and
> emacs in its own Xwindow works if you're directly on the machine.
However,
> emacs will not open without the -nw option thru ssh.  (Even though it did
> while the machine was running for quite some time.)  Restarting the
machine
> fixes the problem.

Can you do "netstat -a" (look for listening ports in the 6000-6100 range)
when the problem occurs ?
Also, do "echo $DISPLAY".

Try to run "naked" emacs - emacs -q , what happens ?

Ehud.


--
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 GnuPG: 98EA398D <http://www.keyserver.net/>    Better Safe Than Sorry

RE: Weird emacs behavior

[Leo Chang]

Weirdly enough, this behavior went away when I tried it this morning (after
a couple of days).  Emacs is working again.  I can't explain it at all.

-----Original Message-----
From: Ehud Karni [mailto:ehud@unix.mvs.co.il] 
Sent: Wednesday, February 01, 2006 7:46 AM
To: lchang@clickshift.com
Cc: help-gnu-emacs@gnu.org; bug-gnu-emacs@gnu.org
Subject: Re: Weird emacs behavior

 [ resent, there was a mistake in the mailing list name ]

On Mon, 30 Jan 2006 22:38:16 -0800, Leo Chang wrote:
>
> There is an unexplained behavior that we've seen on a few machines we have
> with emacs.  These are Redhat Enterprise Linux boxes that we usually ssh
to.
> Xforwarding works fine.  All X apps including emacs work fine.  Then,
after
> a long time (weeks or months), emacs stops appearing in its own window
when
> you ssh into the box.  Instead, after a long wait, it croaks with
something
> like "Connection Lost to Xserver. localhost 10:0."
>
> At this point, you can open ALL X applications except for emacs.  Xeyes,
> xclock, xterm, firefox all work!  But not emacs.  "emacs -nw" does work,
and
> emacs in its own Xwindow works if you're directly on the machine.
However,
> emacs will not open without the -nw option thru ssh.  (Even though it did
> while the machine was running for quite some time.)  Restarting the
machine
> fixes the problem.

Can you do "netstat -a" (look for listening ports in the 6000-6100 range)
when the problem occurs ?
Also, do "echo $DISPLAY".

Try to run "naked" emacs - emacs -q , what happens ?

Ehud.


--
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 GnuPG: 98EA398D <http://www.keyserver.net/>    Better Safe Than Sorry