[Xquartz-dev] keyboard/mouse focus issues

Pelle Johansson pelle at morth.org
Fri Oct 16 12:13:07 PDT 2009


No, not yet, but I'll make sure to try that. I haven't actually  
downloaded alpha3 yet, I'm running the server tip from Oct 13 right  
now...
This made me remember when I first saw this issue. It was just before  
alpha1 was released when I was trying to build the 1.6 server  
anyway... I thought then that I messed it up somehow, that's why I  
didn't bring it up myself.

One strange thing I noticed now while testing is that the events are  
delivered when I minimize the window, so they have to be queued up  
somewhere, but stuck, and then when the window is minimized they  
finally get unstuck. They are all sent to the window minimized last.

This is easily reproducable if you have the issue:
start two xev
get the server stuck
type a key into one of the windows
change front window using the window menu
type another key
make sure the window you want to minimize first is the active one
minimize using the window menu.

You should see all the KeyPress and KeyRelease events delivered to the  
window minimized last, can someone reproduce this?
-- 
Pelle Johansson

16 okt 2009 kl. 20.33 skrev Jeremy Huddleston:

> Did you try nuking the xkb directory with the alpha3 shipped server  
> or using the alpha1 server binary in alpha3?  So many libs changed  
> during alpha1 to alpha3 that I want to eliminate client-side issues.
>
> --Jeremy
>
> On Oct 16, 2009, at 10:16, Pelle Johansson wrote:
>
>> Hrm, I just noticed I can only reproduce it if I actually click an  
>> X11 window to make X11 active. If I click the dock item the windows  
>> work. As usual minimizing all the windows and restoring them  
>> resolves the issue. gitk is also affected btw (was just looking  
>> though the changes to see if I can spot something).
>> -- 
>> Pelle Johansson
>>
>> 16 okt 2009 kl. 15.57 skrev Jeremy Huddleston:
>>
>>> hrm... ok.  Thanks for the info.  I'll be building some versions  
>>> of the server incrementally from what was released in alpha1  
>>> through what is in alpha3 and will let you know when they're  
>>> available... hopefully with these we can atleast hone in on the  
>>> problematic change.
>>>
>>> In the mean time, can you atleast confirm two things for me?
>>>
>>> 1) Test my xkb hunch:
>>> Install alpha3
>>> Nuke the /opt/X11/share/X11/xkb directory
>>> Does the problem go away? (note that the 1.7 server will fail to  
>>> startup this way)
>>>
>>> 2) Ensure it is actually a server bug:
>>> Install alpha1.
>>> Backup its X11.bin
>>> cp /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin /tmp/ 
>>> X11.bin.alpha1
>>> Install alpha3
>>> Restore alpha1's X11.bin
>>> sudo cp /tmp/X11.bin.alpha1 /Applications/Utilities/XQuartz.app/ 
>>> Contents/MacOS/X11.bin
>>> Nuke the /opt/X11/share/X11/xkb directory (important since  
>>> alpha1's X11.bin fails keymapping if that directory is in place)
>>>
>>> The resulting install *should* work if my assumption is correct  
>>> that it's a server related issue
>>>
>>> Thanks,
>>> Jeremy
>>>
>>> On Oct 16, 2009, at 01:29, John Koren wrote:
>>>
>>>> Jeremy,
>>>>
>>>> I use rxvt and xterm and both lock up equally with alpha2 and  
>>>> alpha3
>>>> with or without X11.bin-1.7.0901. Unfortunately, I do not have time
>>>> for debugging and thus I am just monitoring closely this issue.  
>>>> alpha1
>>>> is working adequately for me (with some strange but relatively  
>>>> minor
>>>> issues).
>>>>
>>>> -John
>>>>
>>>> On Thu, Oct 15, 2009 at 10:46 PM, Jeremy Huddleston <jeremyhu at apple.com 
>>>> > wrote:
>>>>> So, I've been trying for an hour or so, and I can't seem to  
>>>>> reproduce this
>>>>> bug where mouse/keyboard events stop being sent when switching  
>>>>> to/from X11
>>>>> as the focused application.
>>>>>
>>>>> I haven't heard much since alpha3, but I'm wondering if that's  
>>>>> because
>>>>> people are too scared to try alpha3 after the problems mentioned  
>>>>> with
>>>>> alpha2.  I really want to squash this issue since it's the only  
>>>>> problem I am
>>>>> aware of with this release, but I need some help to actually  
>>>>> reproduce it.
>>>>>
>>>>> Can someone please confirm whether or not this issue is still  
>>>>> present in
>>>>> alpha3?  Also, please confirm that it's there in the 1.7 server  
>>>>> as well as
>>>>> the 1.6 server shipped.
>>>>>
>>>>> I'll be building a bunch of "drop in" server binaries for  
>>>>> testing if I can't
>>>>> actually reproduce this myself.
>>>>>
>>>>> Thanks,
>>>>> Jeremy
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Xquartz-dev mailing list
>>>>> Xquartz-dev at lists.macosforge.org
>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>>>>>
>>>>>
>>>> _______________________________________________
>>>> Xquartz-dev mailing list
>>>> Xquartz-dev at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>>>
>>> _______________________________________________
>>> Xquartz-dev mailing list
>>> Xquartz-dev at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>>
>> _______________________________________________
>> Xquartz-dev mailing list
>> Xquartz-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev



More information about the Xquartz-dev mailing list