I've just finished uploading the first release candidate for the next X11 package installer. You can find it here: http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc). As of 2.3.0-rc1, the server bits are actually located in the bundle. / usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side-effects to note: If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding. You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over /Applications/Utilities/ X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz. ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
Jeremy, Just tried it on top of 2.2.1. Doesn't work. I get: 5/12/08 8:28:56 PM org.x.startx[8835] Xquartz: Could not find a new enough X11.app LSFindApplicationForInfo() returned 5/12/08 8:28:56 PM org.x.startx[8835] X11.app = /Applications/ Utilities/X11.app 5/12/08 8:28:56 PM org.x.startx[8835] Version = Unknown (0), Expected Version > 2.3.0 intermixed with other message...over and over and over....infinite loop! Merle On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side- effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
What is the bundle version of /Applications/Utilities/X11.app ? Browse to it in Finder. Have you moved or copied X11.app anywhere? On May 12, 2008, at 17:31, Merle Reinhart wrote:
Jeremy,
Just tried it on top of 2.2.1. Doesn't work. I get: 5/12/08 8:28:56 PM org.x.startx[8835] Xquartz: Could not find a new enough X11.app LSFindApplicationForInfo() returned 5/12/08 8:28:56 PM org.x.startx[8835] X11.app = / Applications/Utilities/X11.app 5/12/08 8:28:56 PM org.x.startx[8835] Version = Unknown (0), Expected Version > 2.3.0 intermixed with other message...over and over and over....infinite loop!
Merle
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side- effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
ugg. I left out Info.plist from EXTRA_DIST in the source tarball, so it wasn't installed to the .app bundle. Place these two files at /Applications/Utilities/X11.app/Contents --Jeremy On May 12, 2008, at 17:31, Merle Reinhart wrote:
Jeremy,
Just tried it on top of 2.2.1. Doesn't work. I get: 5/12/08 8:28:56 PM org.x.startx[8835] Xquartz: Could not find a new enough X11.app LSFindApplicationForInfo() returned 5/12/08 8:28:56 PM org.x.startx[8835] X11.app = / Applications/Utilities/X11.app 5/12/08 8:28:56 PM org.x.startx[8835] Version = Unknown (0), Expected Version > 2.3.0 intermixed with other message...over and over and over....infinite loop!
Merle
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side- effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
It starts up just fine now. Looking at /Applications/Utilities/X11.app/Contents, it looks like the files CodeResources and version.plist are from March 5 from one of the previous installs. I'll start putting it through some of my workflow. Thanks! Merle On May 12, 2008, at 8:58 PM, Jeremy Huddleston wrote:
ugg. I left out Info.plist from EXTRA_DIST in the source tarball, so it wasn't installed to the .app bundle.
Place these two files at /Applications/Utilities/X11.app/Contents
<Info.plist><PkgInfo>
--Jeremy
On May 12, 2008, at 17:31, Merle Reinhart wrote:
Jeremy,
Just tried it on top of 2.2.1. Doesn't work. I get: 5/12/08 8:28:56 PM org.x.startx[8835] Xquartz: Could not find a new enough X11.app LSFindApplicationForInfo() returned 5/12/08 8:28:56 PM org.x.startx[8835] X11.app = / Applications/Utilities/X11.app 5/12/08 8:28:56 PM org.x.startx[8835] Version = Unknown (0), Expected Version > 2.3.0 intermixed with other message...over and over and over....infinite loop!
Merle
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side-effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
Ok, I put up an rc2 which just has the Info.plist and PkgInfo now... not sure what the CodeResources and version.plist files are... but it's working fine on my system without them... not sure what those are for... hmm... /shrug --Jeremy On May 12, 2008, at 18:05, Merle Reinhart wrote:
It starts up just fine now.
Looking at /Applications/Utilities/X11.app/Contents, it looks like the files CodeResources and version.plist are from March 5 from one of the previous installs.
I'll start putting it through some of my workflow.
Thanks!
Merle
On May 12, 2008, at 8:58 PM, Jeremy Huddleston wrote:
ugg. I left out Info.plist from EXTRA_DIST in the source tarball, so it wasn't installed to the .app bundle.
Place these two files at /Applications/Utilities/X11.app/Contents
<Info.plist><PkgInfo>
--Jeremy
On May 12, 2008, at 17:31, Merle Reinhart wrote:
Jeremy,
Just tried it on top of 2.2.1. Doesn't work. I get: 5/12/08 8:28:56 PM org.x.startx[8835] Xquartz: Could not find a new enough X11.app LSFindApplicationForInfo() returned 5/12/08 8:28:56 PM org.x.startx[8835] X11.app = / Applications/Utilities/X11.app 5/12/08 8:28:56 PM org.x.startx[8835] Version = Unknown (0), Expected Version > 2.3.0 intermixed with other message...over and over and over....infinite loop!
Merle
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side-effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
[ http://xquartz.macosforge.org/downloads/X11-2.3.0_rc2.pkg ] Jeremy Huddleston wrote:
Ok, I put up an rc2 which just has the Info.plist and PkgInfo now... not sure what the CodeResources and version.plist files are... but it's working fine on my system without them... not sure what those are for... hmm...
/shrug
--Jeremy
On May 12, 2008, at 18:05, Merle Reinhart wrote:
It starts up just fine now.
Looking at /Applications/Utilities/X11.app/Contents, it looks like the files CodeResources and version.plist are from March 5 from one of the previous installs.
I'll start putting it through some of my workflow.
Thanks!
Merle
On May 12, 2008, at 8:58 PM, Jeremy Huddleston wrote:
ugg. I left out Info.plist from EXTRA_DIST in the source tarball, so it wasn't installed to the .app bundle.
Place these two files at /Applications/Utilities/X11.app/Contents
<Info.plist><PkgInfo>
--Jeremy
On May 12, 2008, at 17:31, Merle Reinhart wrote:
Jeremy,
Just tried it on top of 2.2.1. Doesn't work. I get: 5/12/08 8:28:56 PM org.x.startx[8835] Xquartz: Could not find a new enough X11.app LSFindApplicationForInfo() returned 5/12/08 8:28:56 PM org.x.startx[8835] X11.app = /Applications/Utilities/X11.app 5/12/08 8:28:56 PM org.x.startx[8835] Version = Unknown (0), Expected Version > 2.3.0 intermixed with other message...over and over and over....infinite loop!
Merle
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side-effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over /Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
Hi, How about a version for those of us that are smart enough to reinstall when 10.5.3 comes out? Or is there a work around so I can install it on 10.5.2? Or do I not have too long to wait for 10.5.3. ;) Jamie On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side- effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
To be honest, I've been pretty much sitting on this since about Thursday. I wanted to wait until 10.5.3 was out to avoid possible clobber issues that I saw resulting from the new startup code... but someone who has access to the developer seeds needed some of these fixes in pkg form, so I figured I'd push it out. For the rest of you, you'll get most of these updates just by installing 2.2.1 and dropping in the http://xquartz.macosforge.org/downloads/Xquartz-1.4.0- apple8.bz2 update. I think the only thing I've changed since then has been the startup path, so you're not really missing much. --Jeremy On May 13, 2008, at 08:22, Jamie Kennea wrote:
Hi,
How about a version for those of us that are smart enough to reinstall when 10.5.3 comes out? Or is there a work around so I can install it on 10.5.2?
Or do I not have too long to wait for 10.5.3. ;)
Jamie
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side- effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
10.5.3 can be found where? I'm an ADC member, but not seeing it, so I'm curious. Thanks, Robert Jeremy Huddleston wrote:
To be honest, I've been pretty much sitting on this since about Thursday. I wanted to wait until 10.5.3 was out to avoid possible clobber issues that I saw resulting from the new startup code... but someone who has access to the developer seeds needed some of these fixes in pkg form, so I figured I'd push it out. For the rest of you, you'll get most of these updates just by installing 2.2.1 and dropping in the http://xquartz.macosforge.org/downloads/Xquartz-1.4.0-apple8.bz2 update. I think the only thing I've changed since then has been the startup path, so you're not really missing much.
--Jeremy
On May 13, 2008, at 08:22, Jamie Kennea wrote:
Hi,
How about a version for those of us that are smart enough to reinstall when 10.5.3 comes out? Or is there a work around so I can install it on 10.5.2?
Or do I not have too long to wait for 10.5.3. ;)
Jamie
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side-effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over /Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
You have to be a Select or Premier level member to have access. Merle On May 13, 2008, at 12:19 PM, Chupacerveza wrote:
10.5.3 can be found where? I'm an ADC member, but not seeing it, so I'm curious.
Thanks, Robert
Jeremy Huddleston wrote:
To be honest, I've been pretty much sitting on this since about Thursday. I wanted to wait until 10.5.3 was out to avoid possible clobber issues that I saw resulting from the new startup code... but someone who has access to the developer seeds needed some of these fixes in pkg form, so I figured I'd push it out. For the rest of you, you'll get most of these updates just by installing 2.2.1 and dropping in the http://xquartz.macosforge.org/downloads/Xquartz-1.4.0-apple8.bz2 update. I think the only thing I've changed since then has been the startup path, so you're not really missing much. --Jeremy On May 13, 2008, at 08:22, Jamie Kennea wrote:
Hi,
How about a version for those of us that are smart enough to reinstall when 10.5.3 comes out? Or is there a work around so I can install it on 10.5.2?
Or do I not have too long to wait for 10.5.3. ;)
Jamie
On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
I've just finished uploading the first release candidate for the next X11 package installer. You can find it here:
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
Some notes (IMPORTANT, READ ME!!!): The installer requires 10.5.3, so if you don't have access to a seed of 10.5.3, you'll have to wait until release. This package doesn't "really" need 10.5.3, but I don't want people to install the 10.5.3 OS update after this package and then forget to reinstall X11 because it will cause some issues due to the new startup mechanism (you'll loose the X11 menus, etc).
As of 2.3.0-rc1, the server bits are actually located in the bundle. /usr/X11/bin/Xquartz is just a stub that "does the right thing" to start the server (for now, it's just doing an exec(), but it will be done via Mach-IPC in the future). This allowed us to clean out all the extra cruft we had in xinit. There are some side-effects to note:
If you copied or moved your X11.app bundle from its default location, you will need to update the copy with the new one after installation. If you don't, you run the risk that /usr/X11/bin/ Xquartz will find the old one and you'll see messages to Console.app indicating this. If X11 fails to start after updating to 2.3.0, this is the most likely culprit. Check Console.app for debugging messages that will tell you the location of X11.app that Xquartz is finding.
You will not be able to use any of the Xquartz binaries from previous releases with this release, and visa-versa. That is why I haven't made an updated binary drop for a while. From now on, you'll need to grab X11-1.4.0-appleXX.bz2 and drop it over / Applications/Utilities/X11.app/Contents/MacOS/X11 rather than updating /usr/X11/bin/Xquartz.
ChangeLog: http://xquartz.macosforge.org/trac/wiki/ChangeLog
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
Hi, Just installed 10.5.3 and 2.3.0-rc2 and I've noticed that the control key gets "stuck" when using it to switch spaces with X11. E.g.: I have an xterm in space 1. I click on the one in space 1 to activate it, and use control+left arrow to switch to space 2, the control+right arrow to go back to space 1. Clicking on the xterm now brings up the xterm menu, as if I pressed control while clicking. Pressing the control key again seems to clear the stuck key. Cheers, Jamie
+ Jamie Kennea <jamie@pompey.org>:
Just installed 10.5.3 and 2.3.0-rc2 and I've noticed that the control key gets "stuck" when using it to switch spaces with X11. E.g.:
I have an xterm in space 1.
I click on the one in space 1 to activate it, and use control+left arrow to switch to space 2, the control+right arrow to go back to space 1.
Clicking on the xterm now brings up the xterm menu, as if I pressed control while clicking. Pressing the control key again seems to clear the stuck key.
Yep, I am seeing this. Some others are seeing it too, others are unable to reproduce the problem. Nobody seems to know why. - Harald
On May 28, 2008, at 3:38 PM, Harald Hanche-Olsen wrote:
Yep, I am seeing this. Some others are seeing it too, others are unable to reproduce the problem. Nobody seems to know why.
Hmm... now I have a stuck shift key, but only for non-letter keys. I.e. typing: abc,./;'[]\ shows this in the xterm: abc<>?:"{}| How bizarre. Pressing shift doesn't fix it either. I had to restart X11. :( Jamie
I've noticed this as well sometimes... I've managed to trigger/fix it by holding shift while pressing capslock. --Jeremy On May 28, 2008, at 13:19, Jamie Kennea wrote:
On May 28, 2008, at 3:38 PM, Harald Hanche-Olsen wrote:
Yep, I am seeing this. Some others are seeing it too, others are unable to reproduce the problem. Nobody seems to know why.
Hmm... now I have a stuck shift key, but only for non-letter keys. I.e. typing:
abc,./;'[]\
shows this in the xterm:
abc<>?:"{}|
How bizarre. Pressing shift doesn't fix it either. I had to restart X11. :(
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi, I've found a spaces issue with 2.3.0-rc2 under 10.4.3, relating to a new feature in the 10.4.3 version of Spaces. The Spaces preference now contains a new option, the rather wordy: "When switching to an application, switch to a space with open windows for the application". When this is unchecked, clicking on the Dock icon or using command-tab to select it will not automatically switch the space to the application, so for example you can open a Safari window on another Space by clicking on the Dock icon then pressing command-N. Double clicking on the Dock icon will switch to the Space where the active window is. This is basically the implementation of spaces auto switching that I had been hoping for since Leopard was released, so I'm very happy. However - it doesn't work with X11. Clicking the Dock icon once, or selecting X11 app with cmd-tab still autoswitches to the space where X11 was activated like the old pre 10.4.3 Spaces behaviour, so in essence X11 ignores the Spaces preference setting. Cheers, Jamie
I assume you mean 10.5.3 ;) In any event, please open a bug report for me. This won't be fixed in 2.3.0-rc3 which I'm gonna be rolling in the next day or so... but hopefully I'll be able to get it fixed for 2.3.0-rc4. --Jeremy On May 29, 2008, at 13:46, Jamie Kennea wrote:
Hi,
I've found a spaces issue with 2.3.0-rc2 under 10.4.3, relating to a new feature in the 10.4.3 version of Spaces. The Spaces preference now contains a new option, the rather wordy: "When switching to an application, switch to a space with open windows for the application".
When this is unchecked, clicking on the Dock icon or using command-tab to select it will not automatically switch the space to the application, so for example you can open a Safari window on another Space by clicking on the Dock icon then pressing command-N. Double clicking on the Dock icon will switch to the Space where the active window is.
This is basically the implementation of spaces auto switching that I had been hoping for since Leopard was released, so I'm very happy.
However - it doesn't work with X11. Clicking the Dock icon once, or selecting X11 app with cmd-tab still autoswitches to the space where X11 was activated like the old pre 10.4.3 Spaces behaviour, so in essence X11 ignores the Spaces preference setting.
Cheers,
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (5)
-
Chupacerveza
-
Harald Hanche-Olsen
-
Jamie Kennea
-
Jeremy Huddleston
-
Merle Reinhart