I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2: Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub. Please test it out and let me know of any regressions. http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later... --Jeremy
I expect that 10.5.4 will probably break 2.3.0 if it's installed after it (due to the startup changes). That is the meaning behind the "requirement" ... I assume you are all savvy enough to be ok with installing X11 again after you do an OS update. For everyone else, I'm not going to release 2.3.0 until I know the following OS update will be "safe" for it. --Jeremy On May 30, 2008, at 10:27, Jamie Kennea wrote:
On May 30, 2008, at 1:18 PM, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0.
I assume that 10.5.4 isn't required for this version, as the installer text suggests!
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;) --Jeremy On May 30, 2008, at 10:18, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2:
Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub.
Please test it out and let me know of any regressions.
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg
Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later...
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Ok. Seems to work fine for me. Merle On Jun 3, 2008, at 8:29 PM, Jeremy Huddleston wrote:
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;)
--Jeremy
On May 30, 2008, at 10:18, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2:
Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub.
Please test it out and let me know of any regressions.
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg
Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later...
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Thanks for the feedback. What don't you like about the icon... perhaps that can be addressed? I'm glad to have the new icon because I wanted to start using the new X.org logo rather than the old one. --Jeremy On Jun 3, 2008, at 18:13, Jamie Kennea wrote:
On 3 Jun 2008, at 8:36 pm, Merle Reinhart wrote:
Ok. Seems to work fine for me.
Yep, for me too. Don't like the new icon, but that's not really a bug!
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi Jeremy! Am 04.06.2008 um 04:23 schrieb Jeremy Huddleston:
What don't you like about the icon... perhaps that can be addressed? I'm glad to have the new icon because I wanted to start using the new X.org logo rather than the old one.
See comment #3 of http://xquartz.macosforge.org/trac/ticket/110 I am also glad to see the new icon. Because it reflects the official and recent icon change of X.org. But on Apple desktops it should confirm the Apple Human Interface Guidelines: Creating Icons for Mac OS X v10.5 and Later http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuid... /apple_ref/doc/uid/20000967-SW1 What is lacking to this icon, is a 265x265 pixel version and a 512x512 pixel version. This should be catched up. I have already written a similar email yesterday to Simone, who made this icon(s) heavily based and derived from http://commons.wikimedia.org/wiki/ Image:X.Org_Logo.svg , but no reaction so far from her. The project's website logo on http://xquartz.macosforge.org/trac/wiki should also reflect this icon change, and it should at least match with the one Simone has created for the X11 application. Sierk -- Sierk Bornemann WWW: http://sierkbornemann.de/
On 04.06.2008 at 08:44 Sierk Bornemann wrote:
What is lacking to this icon, is a 265x265 pixel version and a 512x512 pixel version. This should be catched up. I have already written a similar email yesterday to Simone, who made this icon(s) heavily based and derived from http://commons.wikimedia.org/wiki/ Image:X.Org_Logo.svg , but no reaction so far from her.
... just working on a new 512x512 icon. Simone
Hi Simone! Am 04.06.2008 um 21:12 schrieb Simone Karin Lehmann:
... just working on a new 512x512 icon.
Superb! Don't forget to put the 265x265 icon into the .icns file as well. :-) Sierk -- Sierk Bornemann email: sierkb@gmx.de WWW: http://sierkbornemann.de/
Cool beans. Thanks so much, Simone. --Jeremy On Jun 4, 2008, at 12:12, Simone Karin Lehmann wrote:
On 04.06.2008 at 08:44 Sierk Bornemann wrote:
What is lacking to this icon, is a 265x265 pixel version and a 512x512 pixel version. This should be catched up. I have already written a similar email yesterday to Simone, who made this icon(s) heavily based and derived from http://commons.wikimedia.org/wiki/ Image:X.Org_Logo.svg , but no reaction so far from her.
... just working on a new 512x512 icon.
Simone
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On 04.06.2008 at 21:12 Simone Karin Lehmann wrote:
... just working on a new 512x512 icon.
...done. The icon is update and now includes 512x512 and 256x256 versions. It's slightly modified to by adding some light to the borders of the "X", so that it should be more visible on dark backgrounds too. I've reopened the ticket and attached the updated icon. http://xquartz.macosforge.org/trac/ticket/110#comment:3 Simone
On Jun 3, 2008, at 10:23 PM, Jeremy Huddleston wrote:
What don't you like about the icon... perhaps that can be addressed? I'm glad to have the new icon because I wanted to start using the new X.org logo rather than the old one.
I like the "solidness" of the old one, it was very easy to see. Perhaps if we could combine the white background of the old icon with the updated X logo that would be the best of both worlds. The new one seems a little to low profile in the dock, almost invisible as its mainly black. But as I say, this is a very minor issue. Jamie
That's a good point. I hadn't actually noticed that since I have a light background. --Jeremy On Jun 4, 2008, at 06:54, Jamie Kennea wrote:
On Jun 3, 2008, at 10:23 PM, Jeremy Huddleston wrote:
What don't you like about the icon... perhaps that can be addressed? I'm glad to have the new icon because I wanted to start using the new X.org logo rather than the old one.
I like the "solidness" of the old one, it was very easy to see. Perhaps if we could combine the white background of the old icon with the updated X logo that would be the best of both worlds. The new one seems a little to low profile in the dock, almost invisible as its mainly black.
But as I say, this is a very minor issue.
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
+ Jeremy Huddleston <jeremyhu@freedesktop.org>:
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;)
Works for me, but I am insanely busy of late and haven't had time to test it properly, I am just using it without much trouble other than some old friends: 1. The "stuck ctrl key" problem. I am pretty sure a bug report is filed on that one, and I do know a workaround (just hit the ctrl key). 2. The exposé bug: Use exposé to reverse the order of windows, click on the top one, and the one below pops forward. Sorry, I just realized I have not filed a bug report for it. You asked me to file one at bugreport.apple.com. I asked if you were sure you wanted it there and not at macosforge.org, but never received an answer, so I forgot about it. 3. Not a problem but a question: I haven't reinstalled Xquartz-1.4.0-apple7 because (a) I have no time to test it anyhow, and (b) I don't know if the Xquartz with 2.3.0-rc3 supersedes it, and (c) I don't know where to put it. It appears that /usr/X11/bin/Xquartz and /Applications/Utilities/X11.app/Contents/MacOS/X11 have traded places? Looks like the former is now just a thin wrapper to start the latter. Should any future Xquartz releases be installed on top of the latter? - Harald
2. The exposé bug: Use exposé to reverse the order of windows, click on the top one, and the one below pops forward. Sorry, I just realized I have not filed a bug report for it. You asked me to file one at bugreport.apple.com. I asked if you were sure you wanted it there and not at macosforge.org, but never received an answer, so I forgot about it.
Report it both places if you're not sure ;) I'm not sure I remember this issue since I've been using exposé without a hitch, so please file the bug to remind me and get it in my queue.
3. Not a problem but a question: I haven't reinstalled Xquartz-1.4.0-apple7 because (a) I have no time to test it anyhow, and (b) I don't know if the Xquartz with 2.3.0-rc3 supersedes it, and (c) I don't know where to put it. It appears that /usr/X11/bin/Xquartz and /Applications/Utilities/X11.app/Contents/MacOS/X11 have traded places? Looks like the former is now just a thin wrapper to start the latter. Should any future Xquartz releases be installed on top of the latter?
Yeah. 2.3.0-rc3 has 1.4.0-apple13 (check X11->About X11). If you want to drop down to 1.4.0-apple7, you'll need to put back the old X11.app as well (your safest bet is to just reinstall 2.2.1 and drop in the binary). I think the server bits entered the .app bundle around apple8 or apple9 (which is why I haven't really announced the incremental changes).
Hello, I have noticed a weird problem that has started with the 2.3.0 rc3 update: I usually connect from my mac to a linux machine through ssh, from where I ssh again to a third linux machine to do actual work (the 3rd machine only allows inbound connections from the second one). Until now, X requests were always correctly forwarded back to the local machine (ie I've always been able to open X applications on the 3rd machine and they showed up correctly on my local display, sorry if I'm not using the appropriate terms). With the rc3, I can't do this anymore -- I get an error message on the 3rd machine telling me the X display cannot be opened (the message says something like "cannot open display on localhost:12.0"). I've just tried this from another mac that hasn't been upgraded to rc3, and it works fine, so nothing has changed on the remote machines (the 3rd machine sets DISPLAY to localhost:10.0 if that's any help). The weird part is that X applications open fine when I launch them on the second machine... I've tried rebooting and trashing the X preferences file, but it doesn't help. This is on an MBP with 10.5.3. Everything works as expected apart from that. Cheers, Vincent On Wed, Jun 4, 2008 at 2:29 AM, Jeremy Huddleston <jeremyhu@freedesktop.org> wrote:
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;)
--Jeremy
On May 30, 2008, at 10:18, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2:
Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub.
Please test it out and let me know of any regressions.
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg
Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later...
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
FWIW, when I follow the steps outlined below with the rc3, I get $ nedit Xlib: connection to "localhost:16.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key NEdit: Can't open display still working fine with previous X (rc2 was working fine IIRC). Cheers V On Wed, Jun 4, 2008 at 8:46 AM, Vincent Noel <vincent.noel@gmail.com> wrote:
Hello,
I have noticed a weird problem that has started with the 2.3.0 rc3 update:
I usually connect from my mac to a linux machine through ssh, from where I ssh again to a third linux machine to do actual work (the 3rd machine only allows inbound connections from the second one). Until now, X requests were always correctly forwarded back to the local machine (ie I've always been able to open X applications on the 3rd machine and they showed up correctly on my local display, sorry if I'm not using the appropriate terms). With the rc3, I can't do this anymore -- I get an error message on the 3rd machine telling me the X display cannot be opened (the message says something like "cannot open display on localhost:12.0").
I've just tried this from another mac that hasn't been upgraded to rc3, and it works fine, so nothing has changed on the remote machines (the 3rd machine sets DISPLAY to localhost:10.0 if that's any help).
The weird part is that X applications open fine when I launch them on the second machine...
I've tried rebooting and trashing the X preferences file, but it doesn't help. This is on an MBP with 10.5.3. Everything works as expected apart from that.
Cheers, Vincent
On Wed, Jun 4, 2008 at 2:29 AM, Jeremy Huddleston <jeremyhu@freedesktop.org> wrote:
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;)
--Jeremy
On May 30, 2008, at 10:18, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2:
Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub.
Please test it out and let me know of any regressions.
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg
Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later...
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I just tried it from my mac, ssh -Y to a solaris 10 machine, then ssh - Y to another solaris 10 machine (I don't have linux boxes readily available). X11 displayed back just fine whether X11 was started on the Mac prior to the ssh's or if the final ssh produces the request to start X11. Merle On Jun 4, 2008, at 6:17 AM, Vincent Noel wrote:
FWIW, when I follow the steps outlined below with the rc3, I get
$ nedit Xlib: connection to "localhost:16.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key NEdit: Can't open display
still working fine with previous X (rc2 was working fine IIRC).
Cheers V
On Wed, Jun 4, 2008 at 8:46 AM, Vincent Noel <vincent.noel@gmail.com> wrote:
Hello,
I have noticed a weird problem that has started with the 2.3.0 rc3 update:
I usually connect from my mac to a linux machine through ssh, from where I ssh again to a third linux machine to do actual work (the 3rd machine only allows inbound connections from the second one). Until now, X requests were always correctly forwarded back to the local machine (ie I've always been able to open X applications on the 3rd machine and they showed up correctly on my local display, sorry if I'm not using the appropriate terms). With the rc3, I can't do this anymore -- I get an error message on the 3rd machine telling me the X display cannot be opened (the message says something like "cannot open display on localhost:12.0").
I've just tried this from another mac that hasn't been upgraded to rc3, and it works fine, so nothing has changed on the remote machines (the 3rd machine sets DISPLAY to localhost:10.0 if that's any help).
The weird part is that X applications open fine when I launch them on the second machine...
I've tried rebooting and trashing the X preferences file, but it doesn't help. This is on an MBP with 10.5.3. Everything works as expected apart from that.
Cheers, Vincent
On Wed, Jun 4, 2008 at 2:29 AM, Jeremy Huddleston <jeremyhu@freedesktop.org> wrote:
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;)
--Jeremy
On May 30, 2008, at 10:18, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2:
Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub.
Please test it out and let me know of any regressions.
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg
Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later...
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Ok, I just checked "Authorize network client connections" in the X preferences (not sure the exact wording in english) and it now works fine. Not sure why this option was unchecked in the first place. Weird. Sorry for the noise. Cheers Vincent On Wed, Jun 4, 2008 at 12:36 PM, Merle Reinhart <merlereinhart@mac.com> wrote:
I just tried it from my mac, ssh -Y to a solaris 10 machine, then ssh - Y to another solaris 10 machine (I don't have linux boxes readily available). X11 displayed back just fine whether X11 was started on the Mac prior to the ssh's or if the final ssh produces the request to start X11.
Merle
On Jun 4, 2008, at 6:17 AM, Vincent Noel wrote:
FWIW, when I follow the steps outlined below with the rc3, I get
$ nedit Xlib: connection to "localhost:16.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key NEdit: Can't open display
still working fine with previous X (rc2 was working fine IIRC).
Cheers V
On Wed, Jun 4, 2008 at 8:46 AM, Vincent Noel <vincent.noel@gmail.com> wrote:
Hello,
I have noticed a weird problem that has started with the 2.3.0 rc3 update:
I usually connect from my mac to a linux machine through ssh, from where I ssh again to a third linux machine to do actual work (the 3rd machine only allows inbound connections from the second one). Until now, X requests were always correctly forwarded back to the local machine (ie I've always been able to open X applications on the 3rd machine and they showed up correctly on my local display, sorry if I'm not using the appropriate terms). With the rc3, I can't do this anymore -- I get an error message on the 3rd machine telling me the X display cannot be opened (the message says something like "cannot open display on localhost:12.0").
I've just tried this from another mac that hasn't been upgraded to rc3, and it works fine, so nothing has changed on the remote machines (the 3rd machine sets DISPLAY to localhost:10.0 if that's any help).
The weird part is that X applications open fine when I launch them on the second machine...
I've tried rebooting and trashing the X preferences file, but it doesn't help. This is on an MBP with 10.5.3. Everything works as expected apart from that.
Cheers, Vincent
On Wed, Jun 4, 2008 at 2:29 AM, Jeremy Huddleston <jeremyhu@freedesktop.org> wrote:
So... I assume the silence is good news? Could I atleast get a few "works for me here" replies so I know that someone other than me is using it and you all haven't lost faith in my betas ;)
--Jeremy
On May 30, 2008, at 10:18, Jeremy Huddleston wrote:
I've uploaded a new release candidate for 2.3.0. I've been using this for about a week now and feel comfortable enough about it to put it out "in the wild" to let you all mess with it while I move on to the next stage of the startup rewrite. Major changes since 2.3.0-rc2:
Pulled in proper xkeyboard-config data instead of xkbdata (this should get Xfake and Xephyr to work without needing the '-kb' command line option) Reverted Xquartz to not use xkb since we don't actually have a quartz keyboard xkb data file (not sure the best way to solve this, I'm going to leave this headache for post-2.3.0) Xquartz now has the capability to add a new $DISPLAY socket after the server is started (rather than only at start). This is needed for the new OSX-friendly startup method that I'm working on. We use this now just within the server itself, but in rc4, I expect the socket will be handed off to the server by the stub.
Please test it out and let me know of any regressions.
http://xquartz.macosforge.org/downloads/X11-2.3.0_rc3.pkg
Note, I consider this fairly stable and regression free at this point, but there are bound to be some issues that arise. Now that I have this out, I'm going to be working on some things that are a bit more fragile, so if you want to balance "works" with "testing", this should be a fairly safe beta for you. Of course, I may end up eating these words later...
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (8)
-
Harald Hanche-Olsen
-
Jamie Kennea
-
Jeremy Huddleston
-
Jeremy Huddleston
-
Merle Reinhart
-
Sierk Bornemann
-
Simone Karin Lehmann
-
Vincent Noel