[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Weird emacs behavior
From: |
Ehud Karni |
Subject: |
Re: Weird emacs behavior |
Date: |
Wed, 1 Feb 2006 14:20:47 +0200 |
On Mon, 30 Jan 2006 22:38:16 -0800, Leo Chang <lchang@clickshift.com> 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.
>
> Has anyone ever seen this behavior? The emacs version is 21.3.1.
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,
Ehud Karni <=