From owner-freebsd-stable Wed Aug 21 6:59:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA54937B400 for ; Wed, 21 Aug 2002 06:59:49 -0700 (PDT) Received: from server.rucus.ru.ac.za (server.rucus.ru.ac.za [146.231.115.1]) by mx1.FreeBSD.org (Postfix) with SMTP id 99E0C43E4A for ; Wed, 21 Aug 2002 06:59:46 -0700 (PDT) (envelope-from drs@rucus.ru.ac.za) Received: (qmail 82920 invoked from network); 21 Aug 2002 13:59:40 -0000 Received: from bashir.dsl.ru.ac.za (146.231.113.19) by server.rucus.ru.ac.za with SMTP; 21 Aug 2002 13:59:40 -0000 Received: (qmail 318 invoked by uid 1001); 21 Aug 2002 13:59:40 -0000 Date: Wed, 21 Aug 2002 15:59:40 +0200 From: David =?iso-8859-1?Q?Sieb=F6rger?= To: "Brian T. Schellenberger" , Steve Tremblett Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: weird X problem Message-ID: <20020821135940.GA309@rucus.ru.ac.za> References: <20020821091517.A16327@sjt-u10.cisco.com> <200208210926.19974.bts@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200208210926.19974.bts@babbleon.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed 2002-08-21 (09:26), Brian T. Schellenberger wrote: > On Wednesday 21 August 2002 09:15 am, Steve Tremblett wrote: > | I just upgraded my laptop to XFree86 4.2 and everything seemed to work, > | but I just discovered a MADDENING problem. > | > | I have xhost lines in my xinitrc to allow remote X programs for a > | handful of machines, but since upgrading 4.0->4.2 those machines can't > | display on the server. I checked the xhost commands, and the hostnames > | are correct. I tried using the IP address instead with no success. > | The workstation can ping the laptop, so it isn't a network problem. It > | all comes down to the laptop not allowing X clients that xhost says it > | should. > | > | Does this ring a bell with anyone? Alternatively, does anyone have any > | suggestions on diagnostics to figure out what's going wrong? > > > I am running into similar problems. I worked around it by ssh'ing to the > system and then displaying through the ssh display connection, but I doubt > that I should ahve to do this. These days, the X server's TCP transport is disabled unless it's started with "startx -listen_tcp". Look up -listen_tcp in startx(1), but SSH's X forwarding is a far more secure alternative. -- David Siebörger drs@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message