Ok, I have a new rc which fixes the last regression I know about (the "Client that triggers launchd to start X11 fails to connect" bug). Please test it out and let me know if there are any other issues that should prevent me from releasing this as 2.3.0. Thanks, Jeremy http://static.macosforge.org/xquartz/downloads/X11-2.3.0_rc7.pkg
On Jul 15, 2008, at 10:39 PM, Jeremy Huddleston wrote:
Ok, I have a new rc which fixes the last regression I know about (the "Client that triggers launchd to start X11 fails to connect" bug). Please test it out and let me know if there are any other issues that should prevent me from releasing this as 2.3.0.
This fixes the problem for me. I do still have the issue of applications ignoring .Xresources if they trigger X11 to start. It would also be nice if X11 applications could get focus after being spawned from Terminal.app. Both of these problems are relatively small problems, though. Thanks, -- Lee Aylward
The .Xresources issue is very complicated and I'm still not sure of the best solution. I was hoping that delaying adding the launchd display file descriptor would solve the problem... and it does, but at the cost of this xauth bug... As for your other issue, goto X11->Preferences->Windows and select 'Focus on new windows' I believe that was added some time during 2.2.X, but I can't recall. In any case, it is in 2.3.0-rc7 which you are using. --Jeremy On Jul 15, 2008, at 21:47, Lee Aylward wrote:
On Jul 15, 2008, at 10:39 PM, Jeremy Huddleston wrote:
Ok, I have a new rc which fixes the last regression I know about (the "Client that triggers launchd to start X11 fails to connect" bug). Please test it out and let me know if there are any other issues that should prevent me from releasing this as 2.3.0.
This fixes the problem for me.
I do still have the issue of applications ignoring .Xresources if they trigger X11 to start. It would also be nice if X11 applications could get focus after being spawned from Terminal.app. Both of these problems are relatively small problems, though.
Thanks, -- Lee Aylward _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I installed it and it seems to fix this problem for me. I'll let you know if I see any other anomalies while using it today. BTW: Any idea when Apple will incorporate any of these updates into their standard Leopard X11 distribution? I am getting close to making a broader distribution of our product and would prefer not to have to field questions about the async hang problem you fixed back in 2.2 ... - Wes On Tue, Jul 15, 2008 at 11:39 PM, Jeremy Huddleston <jeremyhu@apple.com> wrote:
Ok, I have a new rc which fixes the last regression I know about (the "Client that triggers launchd to start X11 fails to connect" bug). Please test it out and let me know if there are any other issues that should prevent me from releasing this as 2.3.0.
Thanks, Jeremy
http://static.macosforge.org/xquartz/downloads/X11-2.3.0_rc7.pkg _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
-- Wesley D. Turner, Ph.D. Kitware, Inc. R&D Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x120
On Jul 15, 2008, at 11:39 PM, Jeremy Huddleston wrote:
Ok, I have a new rc which fixes the last regression I know about (the "Client that triggers launchd to start X11 fails to connect" bug). Please test it out and let me know if there are any other issues that should prevent me from releasing this as 2.3.0.
Does this release include a fix to the stuck modifier key problem? I thought RC6 did but for some reason after using it for a while the problem seemed to return. Jamie
On Jul 16, 2008, at 10:21 AM, Jamie Kennea wrote:
Does this release include a fix to the stuck modifier key problem? I thought RC6 did but for some reason after using it for a while the problem seemed to return.
I'll answer my own question, I've already managed to get caps-lock to stick in RC7. Here's what I see right now, on 2 machines with RC7 installed: Starting with caps-lock off: Press caps-lock: Letters in upper-case as expected Press caps-lock: Letters still in upper-case - BAD Press caps-lock: Letters in upper case (as expected) Press caps-lock: Letters back to lower case - GOOD Not as bad as before, but still a bug. Cheers, Jamie
Yeah, I haven't addressed the stuck modifier key issue. This issue existed in 2.2.x as well, so it's not really a regression... but I don't feel like looking at file descriptor and socket code any more this week, so I'll try taking a look at that. If it's a simple enough fix, then I should be able to get it into 2.3.0. --Jeremy On Jul 16, 2008, at 08:03, Jamie Kennea wrote:
On Jul 16, 2008, at 10:21 AM, Jamie Kennea wrote:
Does this release include a fix to the stuck modifier key problem? I thought RC6 did but for some reason after using it for a while the problem seemed to return.
I'll answer my own question, I've already managed to get caps-lock to stick in RC7. Here's what I see right now, on 2 machines with RC7 installed:
Starting with caps-lock off: Press caps-lock: Letters in upper-case as expected Press caps-lock: Letters still in upper-case - BAD Press caps-lock: Letters in upper case (as expected) Press caps-lock: Letters back to lower case - GOOD
Not as bad as before, but still a bug.
Cheers,
Jamie _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On 16 Jul 08, at 10:32, Jeremy Huddleston wrote:
Yeah, I haven't addressed the stuck modifier key issue. This issue existed in 2.2.x as well, so it's not really a regression... but I don't feel like looking at file descriptor and socket code any more this week, so I'll try taking a look at that. If it's a simple enough fix, then I should be able to get it into 2.3.0.
--Jeremy
Any follow-up on this? I wasn't having this issue at all running rc6, but I just installed the release and I'm getting stuck modifiers again. Not sure if it's related, but I'm also getting intermittent failures to start up: 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Couldn't get uchr or kchr resource 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Fatal server error: 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Could not build a valid keymap. 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] AbortDDX 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Quitting Xquartz...
On 20 Jul 08, at 16:54, Andrew Farmer wrote:
On 16 Jul 08, at 10:32, Jeremy Huddleston wrote:
Yeah, I haven't addressed the stuck modifier key issue. This issue existed in 2.2.x as well, so it's not really a regression... but I don't feel like looking at file descriptor and socket code any more this week, so I'll try taking a look at that. If it's a simple enough fix, then I should be able to get it into 2.3.0.
--Jeremy
Any follow-up on this? I wasn't having this issue at all running rc6, but I just installed the release and I'm getting stuck modifiers again.
Not sure if it's related, but I'm also getting intermittent failures to start up:
7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Couldn't get uchr or kchr resource 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Fatal server error: 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Could not build a valid keymap. 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] AbortDDX 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Quitting Xquartz...
Correction: The issue also existed in rc6. The "good" version appears to have been 2.2.2 or so.
I've had reports of stuck modifiers going all the way back to the original Leopard release. I have not yet addressed it, but plan to in the near future. --Jeremy On Jul 20, 2008, at 16:54, Andrew Farmer wrote:
On 16 Jul 08, at 10:32, Jeremy Huddleston wrote:
Yeah, I haven't addressed the stuck modifier key issue. This issue existed in 2.2.x as well, so it's not really a regression... but I don't feel like looking at file descriptor and socket code any more this week, so I'll try taking a look at that. If it's a simple enough fix, then I should be able to get it into 2.3.0.
--Jeremy
Any follow-up on this? I wasn't having this issue at all running rc6, but I just installed the release and I'm getting stuck modifiers again.
Not sure if it's related, but I'm also getting intermittent failures to start up:
7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Couldn't get uchr or kchr resource 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Fatal server error: 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Could not build a valid keymap. 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] AbortDDX 7/20/08 16:52:51 [0x0-0x33033].org.x.X11[1533] Quitting Xquartz... _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi, When I was looking through log files for the xauth problem I had I noticed this when installing the 2.3.0-rc7 package: Jul 16 11:50:14 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Scanning system font directories to generate X11 font caches Jul 16 11:50:14 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Making fonts.dir for updated directories. Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for HelveLTMM Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for Helvetica LT MM Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for Times LT MM Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for TimesLTMM Jul 16 11:50:28 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Updating FC cache Jul 16 11:50:59 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Done I don't know if those are important messages or not. I also have a "/usr/X11/man 1" directory, but I am unsure if it was this installer that left that. Anyway, this rc seems fine, thanks. mzs
On Jul 16, 2008, at 14:18, xquartz-dev.5.mzs@spamgourmet.com wrote:
Hi,
When I was looking through log files for the xauth problem I had I noticed this when installing the 2.3.0-rc7 package:
Jul 16 11:50:14 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Scanning system font directories to generate X11 font caches Jul 16 11:50:14 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Making fonts.dir for updated directories. Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for HelveLTMM Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:15 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for Helvetica LT MM Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for Times LT MM Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Unknown Type 1 weight "All" Jul 16 11:50:16 grief /private/tmp/scripts.6tDp/./postinstall[2181]: Couldn't determine weight for TimesLTMM Jul 16 11:50:28 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Updating FC cache Jul 16 11:50:59 grief /private/tmp/scripts.6tDp/./postinstall[2181]: font_cache: Done
I don't know if those are important messages or not.
Yeah, those are just "dirty" fonts... nothing to really worry about.
I also have a "/usr/X11/man 1" directory, but I am unsure if it was this installer that left that.
Rr... ugg... Well, that's just leftover crud... the man pages are in /usr/X11/share/ man and there is a symlink from /usr/X11/man to them... They used to be in a directory /usr/X11/man ... so I think the installer moved the old ones out of the way before replacing the man dir with a man symlink... I'll see if I can clean that up in postinst.
participants (6)
-
Andrew Farmer
-
Jamie Kennea
-
Jeremy Huddleston
-
Lee Aylward
-
Wes Turner
-
xquartz-dev.5.mzs＠spamgourmet.com