From owner-freebsd-questions@FreeBSD.ORG Tue Jul 12 07:30:52 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D76D106564A for ; Tue, 12 Jul 2011 07:30:52 +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 5CE908FC08 for ; Tue, 12 Jul 2011 07:30:52 +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 p6C7UpTk097259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 12 Jul 2011 00:30:51 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p6C7Up3W097258; Tue, 12 Jul 2011 00:30:51 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA12707; Tue, 12 Jul 11 00:26:46 PDT Date: Tue, 12 Jul 2011 07:27:15 -0700 From: perryh@pluto.rain.com To: frank@shute.org.uk Message-Id: <4e1c59c3.T5kMrjV/l+lA16KI%perryh@pluto.rain.com> References: <4e1c1f5f.LsZHLb8pZocKlPVV%perryh@pluto.rain.com> <20110712062255.GA45128@orange.esperance-linux.co.uk> In-Reply-To: <20110712062255.GA45128@orange.esperance-linux.co.uk> 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 Subject: Re: ssh -X (X11 forwarding) not working from 6.1 to 8.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 07:30:52 -0000 Frank Shute wrote: > On Tue, Jul 12, 2011 at 03:18:07AM -0700, perryh@pluto.rain.com wrote: > > > > DISPLAY is not getting set in a remote shell started by "ssh -X". ... > Have you tried putting: > > DISPLAY=:0.0 > > in ~/.ssh/environment on the machine that's not setting DISPLAY > properly? Wouldn't that cause the remote app -- which is running on the ssh server -- to (try to) use that machine's own local display? A port-forwarded connection normally has something along the lines of DISPLAY=localhost:10.0 (but it can't be hard-coded, because the "10" part will vary depending on what-all port-forwarded connections exist).