From owner-freebsd-questions@FreeBSD.ORG Sat Jan 12 03:25:01 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 664EBDD7 for ; Sat, 12 Jan 2013 03:25:01 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 4025014F for ; Sat, 12 Jan 2013 03:25:01 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id r0C3Ovi8019001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 11 Jan 2013 19:24:57 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id r0C3OvBj019000; Fri, 11 Jan 2013 19:24:57 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA12654; Fri, 11 Jan 13 19:23:10 PST Date: Fri, 11 Jan 2013 18:23:08 -0800 From: perryh@pluto.rain.com To: cyberleo@cyberleo.net Subject: Re: bogus "No protocol specified" message Message-Id: <50f0c90c.KpdsU8zltL2eIteD%perryh@pluto.rain.com> References: <50ef3c36.DOThr42hGxWWeg6h%perryh@pluto.rain.com> <50EF609F.1090306@cyberleo.net> In-Reply-To: <50EF609F.1090306@cyberleo.net> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2013 03:25:01 -0000 CyberLeo Kitsana wrote: > On 01/10/2013 05:09 PM, Perry Hutchison wrote: > > When trying to open an X application on a remote display, > > I am getting > > > > No protocol specified > > Error: cannot open display: 192.168.200.61:0 > > > > The "No protocol specified" message is bogus: the display is > > specified correctly*, and the same operation -- with exactly > > the same setting of DISPLAY -- was working yesterday ... > > > > What does that message actually mean, and how do I fix it? > > The error is with regards to the X protocol, not the TCP or UNIX socket > protocol. Check that both sides have compatible and matching X authority > information using xauth(1), or that the connecting host or user was > allowed to connect using xhost(1). The problem does indeed have something to do with authority/permission, since "xhost +" fixes it. (Not the best solution, but sufficient to demonstrate where the trouble lies.) I still claim that the message is bogus. It's now perfectly clear that both ends know exactly what protocol to use, and they are using it -- else telling the server to accept all remote connections would have made no difference. The message should mention authority and/or permission, instead of pretending that the client can't figure out what protocol to use because none was "specified".