From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: [OT ssh -Y] Attempting to start emacsclient .. unusual error?
Date: Sun, 11 Jan 2015 16:37:44 -0500 [thread overview]
Message-ID: <87h9vxm21j.fsf@reader.local.lan> (raw)
In-Reply-To: <87387hthxi.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> X11 forwarding request failed on channel 0
>
> Please make sure you have xauth in your PATH on the remote system.
Seems so as reported.
running ssh -vv -Y [...] output might be helpful I guess.
I prunned it down to just after key recognition and such:
But, at least to me, it doesn't seem very informatiive.
[...]
debug2: callback start
debug2: x11_get_proto: /usr/openwin/bin/xauth list :0.0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 1
debug2: fd 4 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug1: Sending command: emacsclient -snognus -c
debug2: channel 0: request exec confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 100 id 0
X11 forwarding request failed on channel 0
debug2: channel 0: rcvd adjust 87380
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug2: channel 0: rcvd ext data 41
emacsclient: could not get terminal name
debug2: channel 0: written 41 to efd 7
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug2: channel 0: rcvd eow
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: rcvd close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 5524, received 3176 bytes, in 0.1 seconds
Bytes per second: sent 50034.4, received 28767.1
debug1: Exit status 1
next prev parent reply other threads:[~2015-01-11 21:37 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 [this message]
2015-01-12 3:39 ` Mike Kupfer
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=87h9vxm21j.fsf@reader.local.lan \
--to=reader@newsguy.com \
--cc=ding@gnus.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.
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).