unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: CVS trunk emacsclient: X11 connection rejected
Date: Mon, 29 Oct 2007 13:57:55 -0400	[thread overview]
Message-ID: <wz7il5n6qk.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvejfg8hvz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 27 Oct 2007 15:51:57 -0400")

Stefan Monnier wrote:

>> I did try a test with an unset XAUTHORITY:
>
> host1> XAUTHORITY= emacs -Q -f server-start &
> host1> ssh host2
> host2> ssh host1 emacsclient --no-wait $PWD/README
>
>> and it didn't seem to help.

OK, so the above definitely doesn't change anything, I still get "X11
connection rejected".

If instead I unset XAUTHORITY before starting Emacs, or set it to
~/.Xauthority, then `ssh host2' warns "No xauth data; using fake
authentication data for X11 forwarding.". I can still open xterms,
emacs, etc. Now the emacsclient command (with no display option) shows
the behaviour of popping up a new frame of the server Emacs showing
scratch, and not visiting the specified file at all.

> What happens if you do
>
>    host2> ssh host1
>    host1> echo "$DISPLAY"

Is that meant to be that way round? I should have used better names
than "host1", "host2". :)

host1 is the local host, running the X session, host2 is a remote host.

> and then use this DISPLAY (presumably somehting like "localhost:10"): go to
> your Emacs and type
>
>    M-: (make-frame-on-display "localhost:10") RET

Assuming you meant:

host1> ssh host2
host2> ssh host1 'echo $DISPLAY'   # localhost:10.0
host2> emacs -Q --eval '(make-frame-on-display "localhost:10.0")'

then it works. If you wanted me to ssh to host1 and start an Emacs
there, then it also works.

If you wanted me to start an Emacs on host1 before `ssh host2', then
it's unresponsive for a few seconds, then reports:
"x-create-frame-with-faces: Display localhost:10.0 can't be opened".

  reply	other threads:[~2007-10-29 17:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  0:57 CVS trunk emacsclient: X11 connection rejected Glenn Morris
2007-10-26  5:24 ` Stefan Monnier
2007-10-27  0:44   ` Glenn Morris
2007-10-27  2:16     ` Stefan Monnier
2007-10-27  2:43       ` Glenn Morris
2007-10-27  3:04         ` Stefan Monnier
2007-10-27  3:33           ` Glenn Morris
2007-10-27 19:51             ` Stefan Monnier
2007-10-29 17:57               ` Glenn Morris [this message]
2007-10-29 18:02                 ` Glenn Morris
2007-10-29 19:16                 ` Stefan Monnier
2007-10-29 20:25                   ` Glenn Morris
2007-10-29 21:01               ` Stefan Monnier
2007-10-29 22:03                 ` Glenn Morris
2007-10-30  2:01                   ` Stefan Monnier
2007-10-26  5:41 ` Jan Djärv
2007-10-27  0:47   ` Glenn Morris

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=wz7il5n6qk.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).