Re: X11 behavior since Tiger and "BadAtom" datapoint

Have you tried not tunneling the X connection? I.e., ***as an experiment*** -- not permanent, try setting your DISPLAY to yourmac:0 and using xhost to allow the 4.2 box. If the error goes away then it's SSH to blame. If not, obviously it's the X server/client(s) interaction more fundamentally.

Have you tried the -Y option to ssh?

On Jun 13, 2006, at 3:44 PM, Mike Zuhl wrote:

I two FreeBSD servers I use: one running FreeBSD 4.2 and one running FreeBSD 5.3. I also connect to a farm of various Linux machines running recent releases. Since Tiger I've been getting the "BadAtom" error on the FreeBSD 4.2 X clients connecting over ssh. These happen when the client tries to get info from the window manager using the xwininfo command or running a TclTk app, which I presumes talks to the window manager for its (somewhat unusual) IPC.

Neither FreeBSD 5.3 nor the recent copies of Linux suffer the same problem. And, strangely, neither does FreeBSD 4.2 when I turn on TCP sockets in X11 and connect directly instead of using ssh.

I suspect that the problem is not X11 but in differences in Tiger's ssh and how it operates with older versions of ssh, both in Sun's and FreeBSD.
--Mike Zuhl
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden

This email sent to email@hidden

"There's no time to stop for gas, we're already late"-- Karin Donker

Rich "wealthychef" Cook

<http://web.mac.com/wealthychef/iWeb/Site/Urinetown.html>

925-784-3077

References:
	>RE: X11 behavior since Tiger and "BadAtom" datapoint (From: Mike Zuhl <email@hidden>)