To summarize, we have confirmation that simply reverting to the alpha1 server binary fixes the problem. I want to now confirm that it is indeed a 1.5 to 1.6 regression rather than something that I've been pushing to both branches. I've built the recent xorg-server binaries for both 1.5 and 1.6:
http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.5.3-apple18.bz2 http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.6.5-apple2.bz2
Please try out alpha2 with this 1.5.3-apple18 binary. My hunch is that it will work, but I want to confirm that before I waste time looking in the wrong places.
Jeremy, I tested alpha 2 and 3 with the same results :-) 1.5.3-apple-18 worked fine, but not 1.6.5-apple2 Christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.
On Oct 20, 2009, at 08:29, Christof Wolf wrote:
To summarize, we have confirmation that simply reverting to the alpha1 server binary fixes the problem. I want to now confirm that it is indeed a 1.5 to 1.6 regression rather than something that I've been pushing to both branches. I've built the recent xorg-server binaries for both 1.5 and 1.6:
http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.5.3-apple18.bz2 http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.6.5-apple2.bz2
Please try out alpha2 with this 1.5.3-apple18 binary. My hunch is that it will work, but I want to confirm that before I waste time looking in the wrong places.
Jeremy,
I tested alpha 2 and 3 with the same results :-)
1.5.3-apple-18 worked fine, but not 1.6.5-apple2
Thanks... so it's definitely a 1.5 to 1.6 issue and not something changing in our DDX... sigh... I have a feeling this is going to be a pain to solve... Those of you seeing this, let's try to figure out why I'm not reproducing it. What are your configurations: laptop/trackpad? keyboard/mouse? tablet? I want to try to mimic your configurations, so I can actually trigger this issue. I'm using these latest builds extensively with no sign of the issue =/ Thanks, Jeremy
Brand new Mac Pro, MacOS 10.6.1. -John
Those of you seeing this, let's try to figure out why I'm not reproducing it. What are your configurations:
laptop/trackpad? keyboard/mouse? tablet?
I want to try to mimic your configurations, so I can actually trigger this issue. I'm using these latest builds extensively with no sign of the issue =/
Thanks, Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I have a summer 2009 MacBook Pro, and use the track pad. I've checked all the settings in the preference dialog one at a time and restarting XQuartz, but there's no difference. FWIW, when the server is working normally and XQuartz is active, a click in the window will still activate the grab in exactly the same way as when the server freezes, but directly after an AllowSome event is sent to remove the grab. -- Pelle Johansson
Thanks... so it's definitely a 1.5 to 1.6 issue and not something changing in our DDX... sigh... I have a feeling this is going to be a pain to solve...
Those of you seeing this, let's try to figure out why I'm not reproducing it. What are your configurations:
laptop/trackpad? keyboard/mouse? tablet?
I want to try to mimic your configurations, so I can actually trigger this issue. I'm using these latest builds extensively with no sign of the issue =/
Thanks, Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Oh, and it won't get stuck (for me anyway) if you click the menu title to activate the window, or use the Dock icon or Exposé. Only a click in the contents of the window will freeze the server. -- Pelle Johansson 20 okt 2009 kl. 21.02 skrev Pelle Johansson:
I have a summer 2009 MacBook Pro, and use the track pad. I've checked all the settings in the preference dialog one at a time and restarting XQuartz, but there's no difference.
FWIW, when the server is working normally and XQuartz is active, a click in the window will still activate the grab in exactly the same way as when the server freezes, but directly after an AllowSome event is sent to remove the grab. -- Pelle Johansson
Thanks... so it's definitely a 1.5 to 1.6 issue and not something changing in our DDX... sigh... I have a feeling this is going to be a pain to solve...
Those of you seeing this, let's try to figure out why I'm not reproducing it. What are your configurations:
laptop/trackpad? keyboard/mouse? tablet?
I want to try to mimic your configurations, so I can actually trigger this issue. I'm using these latest builds extensively with no sign of the issue =/
Thanks, Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (4)
-
Christof Wolf
-
Jeremy Huddleston
-
John Koren
-
Pelle Johansson