On Thursday March 26 2015 15:18:20 Jeremy Huddleston Sequoia wrote: Hi,
> That is quite bizarre. I'm able to run 'DISPLAY=:0.0 /opt/local/bin/xterm' > without issue. A couple of reboots of the VM later, and this issue is back: applications using the Xt from MacPorts won't connect to an X server on :0 or :0.0. The error: xterm: Xt error: Can't open display: :0 Note that this is not a "connection refused" error. This time I've done some more forensics, and unloaded the new org.macports.startx and (ooold!) org.x.startx plists from launchctl, just like I always did with the one from XQuartz. That in itself didn't make any difference, but it is still the case that all applications can connect to a 2nd X server at :1 or :1.0, even those using the Xt from MacPorts. Interestingly, everyone can also connect to the server at :0 when I use DISPLAY=localhost:0 (which should be the same ...) That at least gives me a workaround fix in my .xinitrc, but I'd love to get to the bottom of this. I've been seeing this message in my system.log after logging in, could it be related? /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[153]: The address for `localhost' is a loopback address, not allowed! I'm not sure what this message means, I think /etc/hosts should have a line "127.0.0.1 localhost" like it's always had, and I can't recall ever having seen this message before. Thanks, R. _______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com This email sent to [email protected]
