GNU bug report logs -
#5434
23.1; Emacsclient fails with Rejected Authentication Over SSH
Previous Next
Full log
View this message in rfc822 format
Joel J. Adamson skrev 2010-01-20 17.21:
>
> Please write in English if possible, because the Emacs maintainers
> usually do not have translators to read other languages for them.
>
> Your bug report will be posted to the bug-gnu-emacs <at> gnu.org mailing list,
> and to the gnu.emacs.bug news group.
>
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug:
>
> Having started an Emacs session on<remote-host> (the machine that
> generate this bug report), logging in via ssh and attempting to bring up
> an Emacs frame using 'emacsclient -c' on the local display yields
>
> ,----
> | *ERROR*: Display localhost:10.0 can't be opened
> `----
>
> From Emacs.
>
> ,----
> | $ emacsclient -c
> `----
>
> immediately yields
>
> ,----
> | X11 connection rejected because of wrong authentication.
> `----
>
> This completely disables X11 forwarding FOR EMACSCLIENT ONLY.
> Gnome-terminal still works. Changing default xauth does not help.
> Deleting ~/.Xauthority on localhost and remote-host does not affect the
> problem.
>
> Basically emacsclient doesn't work over ssh. Bummer!
I don't understand your setup.
Do you
1) start Emacs as a daemon on host A.
2) you then ssh in to host A and try to do emacsclient -c?
That won't work if you have ssh X forwarding on, which is what you seem to have.
The emacs daemon runs on display :0 (or something similar), and emacsclient
tries to open your forwarded display, localhost:10, which goes to the host you
came from. This can never work. Please clarify if I misunderstood.
Jan D.
This bug report was last modified 15 years and 177 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.