[Xquartz-dev] 2.3.2_rc3

[George Peter Staplin]

Quoted Jeremy Huddleston <jeremyhu at apple.com>:
> On Dec 7, 2008, at 13:55, Andrew Farmer wrote:
>
>> I'm seeing some weird keyboard-related issues... I'm still   
>> constantly getting the two messages
>>
>>   DarwinPressModifierKey bad keycode: key=7
>>   DarwinPressModifierKey bad keycode: key=5
>
> Yeah, it looks like some keypress combinations aren't reported in the
> keymap.  If you could figure out what combination triggers those, it'd
> be a big help... From what I've seen, they're mostly innocent.

I also see that in the console.app log repeatedly.  I don't know what  
causes it.  I mentioned it to Jordan last night.  I'll look into it,  
if you aren't already.  Are you looking into it?  Though I should  
probably focus on the GLX bugs...

>> in the console, along with one new one:
>>
>>   mieqEnequeue: out-of-order valuator event; dropping.
>
> With 2.3.2_rc3?  Ugg.  This should be fixed now.

I'm seeing this too now.  I can't seem to figure out what causes it, yet.

At least the thread locking is more correct now in the mieqEnqueue  
code.  The segfault that occured before due to the race is gone with  
apps that slow down the X server with heavy rendering.

I'm still not sure about the use of pthreads in parts of the X server,  
but it works for the most part just fine; which is better than I would  
have expected from a program not originally designed for threads,  
before my experience with XQuartz.


George
-- 
http://people.freedesktop.org/~gstaplin/