From: "Leo Chang" <lchang@clickshift.com>
Cc: help-gnu-emacs@gnu.org, bug-gnu-emacs@gnu.org
Subject: RE: Weird emacs behavior
Date: Wed, 1 Feb 2006 11:57:09 -0800 [thread overview]
Message-ID: <E1F4O9I-0002AN-Nc@lists.gnu.org> (raw)
In-Reply-To: <200602011546.k11FkTwQ011347@beta.mvs.co.il>
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
next prev parent reply other threads:[~2006-02-01 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1F3pCX-00043h-3d@lists.gnu.org>
2006-02-01 15:46 ` Weird emacs behavior Ehud Karni
2006-02-01 19:57 ` Leo Chang [this message]
2006-02-01 19:57 ` Leo Chang
2006-01-31 6:40 Leo Chang
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1F4O9I-0002AN-Nc@lists.gnu.org \
--to=lchang@clickshift.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).