Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Kupfer <m.kupfer@acm.org>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: [OT ssh -Y] Attempting to start emacsclient .. unusual error?
Date: Sun, 11 Jan 2015 19:39:28 -0800	[thread overview]
Message-ID: <26348.1421033968@allegro.localdomain> (raw)
In-Reply-To: Your message of "Sun, 11 Jan 2015 09:55:40 -0500." <87sifhnz83.fsf@reader.local.lan>

Harry Putnam wrote:

> It may just be a property of using emacs on Solaris.. there seem to be
> a few of those.

Okay, but from your description, Emacs is actually running on the Gentoo
host, though, not Solaris.  The Solaris host just has the X server.

> ssh -Y (Gentoo linux HOST) "emacsclient -snognus -c"
> (There is an gnus session with a server named nognus running there)
> 
>   X11 forwarding request failed on channel 0
>   emacsclient: could not get terminal name

Do other X-based commands work, e.g., "ssh -Y ... xclock" ?

> In case it matters that Solaris-HOST Xsession (only one user) has had this
> typed into USER's xterm `xhost +' for reasons not related to the subject
> of this post.

Is the "xhost +" still needed?  If not, I would try "xhost -" and see if
that somehow fixes things.  (I do not understand X internals enough to
know whether this is a likely culprit; it's just something I would try
if I were seeing the problem myself.  I would also try "ssh -X" instead
of "ssh -Y".)

Does this problem show up if you ssh in to the Gentoo host from other
hosts?

mike



  parent reply	other threads:[~2015-01-12  3:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 14:55 Harry Putnam
2015-01-11 16:12 ` Andreas Schwab
2015-01-11 21:31   ` Harry Putnam
2015-01-11 21:37   ` Harry Putnam
2015-01-12  3:39 ` Mike Kupfer [this message]
2015-01-12 18:39   ` Harry Putnam

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=26348.1421033968@allegro.localdomain \
    --to=m.kupfer@acm.org \
    --cc=ding@gnus.org \
    --cc=reader@newsguy.com \
    /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).