As noticed by several users running the developer preview version of OS X 10.8 Mountain Lion, Apple is no longer including its X11 application for running software through the X Window System interface. A popular option for scientists and others seeking to run specialized UNIX software both on local machines and across networks, X11 has been available on OS X for a number of years and has been included as a default install since Mac OS X Leopard.
/article-new/2012/02/x11_mountain_lion_alert.jpg?lossy "x11_mountain_lion_alert")
The X Window System has an extensive open source history, with development on the Mac side being handled under the XQuartz project. Apple's X11 application has been based on this effort, although as with many open source projects bundled for use in commercial software, X11 has generally been somewhat behind the latest XQuartz releases. The current version of X11 is 2.6.3, while XQuartz is currently available in version 2.7.0.
With Mountain Lion, Apple seems to eliminating its dedicated support for the X11 application, instead redirecting users to the open source XQuartz project, which it will continue to support.
Top Rated Comments
CrossOver ships their own server and does not actually use anything from Apple's X11 except for quartz-wm. I suggest you contact Codeweavers for access to test versions of Crossover that will work on Mountain Lion.
As with most updates, MacPorts will need to adjust to this change. We're working on it, and you can follow the thread I started on macports-dev for specific information.
----------
Please use the latest rc version of XQuartz (currently 2.7.1_rc4). As you probably discovered, earlier versions (like 2.7.0) don't fixup some things.
That's not true. XQuartz sets $DISPLAY for you (and always has). You need to logout and log back in to get $DISPLAY. This is mentioned on the download page and in the installer.
----------
What do you mean? The entire startup sequence for XQuartz is based on xinit and startx. If you're having issues, please file bug reports with specific information.
About what? File bugs, and they'll get fixed in time. I can't fix bugs I don't know about ;)
----------
Note that All of X11 is based off of public APIs except for a small set of "private" APIs in a library that lives at /usr/lib/libXplugin.dylib ... as long as that library is updated for future releases, it should "just work"
Yeah, but seeing as how the "open source XQuartz team" is 99% @apple.com, I think that's probably not difficult...
Actually versions of XQuartz that work with Mountain Lion were released well in advance of Mountain Lion. You just need to be using the rc versions of XQuartz. 2.7.1_rc4 works great with it.
----------
Yes.
----------
File bug reports.
You installed the wrong version. Install 2.7.1_rc4.
----------
It is a valid concern. Please report problems.
No, but I will fix bugs if you report them. gimp runs fine here, but I'm by no means a gimp power user.
Yeah. What they ought to do is release some sort of "Developer Preview" 5 or 6 months ahead of the release of the new OS so that developers heard about these things and had time to produce fixes.
Do you really know what you're talking about? It seems like you really don't know what you're talking about in many respects.
Stuff like this should really be optional. Not everyone uses it.
Anyone who was using X11 on OS X (myself included) never really bothered with Apple's version anyhow and went straight to XQuartz.
So, the facts are:
* Xquartz is the open source X11-compatible window server for Mac OS X
* Xquartz is maintained by Apple-employed developers. It's an Apple-sponsored open source project.
* The 'X11' app bundled with various OS X releases has historically been a snapshot of the Xquartz code, renamed and integrated with the Mac OS X release.
* There was some extra 'glue' which made the Xquartz snapshot known as X11.app behave extra nice with OS X ($DISPLAY setting, etc)
So the actual change in Mountain Lion is that:
* Apple will no longer be bundling re-labelled Xquartz versions with OS X.
* OS X will instead prompt the user to download Xquartz when an X11-dependent application runs.
Now, clearly there's been a shift in responsibility here. The OS X team no longer take responsibility for integrating Xquartz (branded 'X11') into OS X major releases.
Rather, the Xquartz team (still Apple employees, remember) need to build up their process for producing releases independently of the OS X team. This is where the 'glue's got lost. Whatever OS X used to do for X11.app/Xquartz, Xquartz is now going to have to do for itself. From their point of view, it's almost certainly too early to start down that road since ML is still such a moving target. Hence the lack of integration in the present DP state.
I'm failing to see the malice, neglect or otherwise here. Rather, it's letting the Xquartz team control their schedule and deliver their updates independently of OS X without having to rely on people seeking out and installing Xquartz on their own.
Bear in mind also that the third-party developers will also take a little bit to adjust. They've been used to being able to test against 'the X11 that comes with <OSX_VERSION>. Instead, they'll need to test against the current release of Xquartz.
We're only about 24hrs into Mountain Lion's public history... so let's give everyone involved a chance to sort things out.