So, here's the issue -- in order for the launchd support to work, launchd *has* to be the program that executes
X11.app. If not, launchd will not pass the sockets to Xquartz.
How are you connecting to the remote host? If you're using ssh, then running "ssh -X remotehost" should cause X11.app to start when ssh sets up the X11 tunnel. Otherwise, almost any operation on the "file" pointed to by $DISPLAY will cause launchd to start X11, so you could just even include the line 'cat $DISPLAY' in a script.
On Oct 27, 2007, at 8:33 PM, Chris Linstid wrote:
Thanks Ben, that information is extremely helpful.
For work, I use almost exclusively remote X11 applications. What is the correct way to manually start X11 without starting an xterm? I basically never use local xterms. I use rxvt, gnome-terminal, etc. or remote terminals with a local display.
If I attempt to run rxvt or gnome-terminal from Terminal, should X11 automatically start?
It looks like I'm going to have some adapting to do with the new system, but hopefully it will make your work easier. :)
On Oct 27, 2007, at 4:29 PM, Martin Costabel wrote:
> > Thus double-clicking X11.app (the one in /Applications/Utilities) is > basically equivalent to running the command "open-x11 xterm" in Tiger. > > Your ~/.xinitrc is executed, but only after the xterm command.
> > On Leopard, you often don't need to start X11.app yourself. Just run > a command like xterm or start an application that needs X11, and X11 > will start up automatically.
Thanks. I've been meaning to get some real release notes out there,
but instead, let's have some casual, off the cuff ones!
Biggest architectural change in Leopard for X11: Switched from XFree86 codebase (based on, IIRC, X11R6.8) to
X.org codebase (X11R7.2)
Biggest user-visible change: launchd support for X11. The only situation where you should need to manually start X11.app is if you are only running remote X11 applications.
The way that this is accomplished is by some slight-of-hand with the $DISPLAY variable -- if you look, it should be something like "/tmp/ launch-vbXRyu/:0". If an X client connects to this, it will actually
connect to launchd, which will start Xquartz if needed and pass the client's socket to the server.
All of that should be invisible to you; the X client library (libX11.dylib) was modified to support this, and all X11 applications
link against this library. "DISPLAY=:0" would still work if X11.app is already running, but it will not trigger X11 to launch.
Two biggest bugs: * Fullscreen support is broken. I know many of you will hate me for
this -- it stopped working when we switched codebases, and I was unable to get it working again. I'm hoping that some of you developers may be able to help me us fix this. Until then, those of you who need this functionality should be able to use the X11 package
from Tiger instead. (Yes, I know you can't officially download that from www.apple.com -- I would like to see that change and am working
on making that happen; no ETA. You may be able to find a copy of it lying around somewhere.)
* Do not start X11.app from the Dock. It will do strange things -- you'll get two icons. This is due to the aforementioned "launcher"
in /Applications/Utilities/X11.app not being the same as the real server, which is now located at /usr/X11/X11.app.
I sincerely hope that you all will like the new X server -- while it may look the same, it's based a much more modern codebase, and I hope
to be able to facilitate more rapid development on it so that we -- the X11.app-using community -- can make it the best X server possible, on any platform.
Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
_______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden