Date: Wed, 21 Aug 2002 15:59:40 +0200 From: David =?iso-8859-1?Q?Sieb=F6rger?= <drs@rucus.ru.ac.za> To: "Brian T. Schellenberger" <bts@babbleon.org>, Steve Tremblett <sjt@cisco.com> Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: weird X problem Message-ID: <20020821135940.GA309@rucus.ru.ac.za> In-Reply-To: <200208210926.19974.bts@babbleon.org> References: <20020821091517.A16327@sjt-u10.cisco.com> <200208210926.19974.bts@babbleon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020821135940.GA309>