From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= Newsgroups: gmane.emacs.devel Subject: Re: CVS trunk emacsclient: X11 connection rejected Date: Fri, 26 Oct 2007 07:41:09 +0200 Message-ID: <47217DF5.301@swipnet.se> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1193377334 13665 80.91.229.12 (26 Oct 2007 05:42:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 26 Oct 2007 05:42:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 26 07:42:16 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IlHxV-0004KR-04 for ged-emacs-devel@m.gmane.org; Fri, 26 Oct 2007 07:42:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IlHxM-0004bv-2I for ged-emacs-devel@m.gmane.org; Fri, 26 Oct 2007 01:42:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IlHxF-0004ZL-JI for emacs-devel@gnu.org; Fri, 26 Oct 2007 01:41:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IlHxD-0004U6-T8 for emacs-devel@gnu.org; Fri, 26 Oct 2007 01:41:56 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IlHxD-0004Ti-FS for emacs-devel@gnu.org; Fri, 26 Oct 2007 01:41:55 -0400 Original-Received: from av10-2-sn2.hy.skanova.net ([81.228.8.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IlHxC-0000sH-5Z for emacs-devel@gnu.org; Fri, 26 Oct 2007 01:41:54 -0400 Original-Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502) id 443D938005; Fri, 26 Oct 2007 07:41:52 +0200 (CEST) Original-Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP id 2F80137EFB; Fri, 26 Oct 2007 07:41:52 +0200 (CEST) Original-Received: from husetbladh.homeip.net (90-231-102-24-no59.tbcn.telia.com [90.231.102.24]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 0F8DE37E44; Fri, 26 Oct 2007 07:41:51 +0200 (CEST) User-Agent: Thunderbird 2.0.0.6 (X11/20071008) In-Reply-To: X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:81749 Archived-At: Glenn Morris skrev: > With Emacs 22, and two GNU/Linux hosts with a common (NFS) > file-system, I can do this: > >>>From an X-session running on host1: > > host1> emacs -Q -f server-start & > host1> ssh host2 > host2> ssh host1 emacsclient --no-wait $PWD/README > > which visits the README file in the Emacs running on host1. I often > find this convenient, because I often ssh between various machines and > want to have a single Emacs instance. (The "emacsclient" part is > hidden inside an "emacs" wrapper script that Does The Right Thing > according to the situation.) > > If I try the same thing with the CVS trunk, then I get the following > error when trying to run emacsclient: > > X11 connection rejected because of wrong authentication. This is a ssh error message. It usually means that forwarding is not working and sometimes the X11UseLocalhost option to sshd fixes it. I think in your case the first emacs you start has a different DISPLAY than emacsclient and then the ~/.Xauthority does not match. Maybe an ssh(d) upgrade caused this problem? Or as you indicate, the multitty stuff has changed how Emacs uses DISPLAY:s. IT can also be so simple as some of your home directories can't be written to or ~/.Xauthority is not writable. I guess you have to run sshd with -v (or .d ) to exactly see what is going on. Jan D.