Date: Thu, 10 Jan 2013 18:45:19 -0600 From: CyberLeo Kitsana <cyberleo@cyberleo.net> To: Perry Hutchison <perryh@pluto.rain.com> Cc: freebsd-questions@freebsd.org Subject: Re: bogus "No protocol specified" message Message-ID: <50EF609F.1090306@cyberleo.net> In-Reply-To: <50ef3c36.DOThr42hGxWWeg6h%perryh@pluto.rain.com> References: <50ef3c36.DOThr42hGxWWeg6h%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. There's > no problem with network connectivity between the two systems: > ping and rlogin both work in either direction, and the specified > X server is running and accepting connections. > > 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). -- Fuzzy love, -CyberLeo Furry Peace! - http://www.fur.com/peace/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50EF609F.1090306>