[Xquartz-dev] keyboard/mouse focus issues
jpkoren at gmail.com
Sat Oct 17 14:04:05 PDT 2009
sorry for the delay in my reply. I finished the test you asked for.
On Fri, Oct 16, 2009 at 6:57 AM, Jeremy Huddleston <jeremyhu at apple.com> wrote:
> 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)
This did not help. The problem persists.
> 2) Ensure it is actually a server bug:
> Install alpha1.
> Backup its X11.bin
> cp /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
> Install alpha3
> Restore alpha1's X11.bin
> sudo cp /tmp/X11.bin.alpha1
> 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
You are right, yes, this works.
> On Oct 16, 2009, at 01:29, John Koren wrote:
>> 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
>> On Thu, Oct 15, 2009 at 10:46 PM, Jeremy Huddleston <jeremyhu at apple.com>
>>> So, I've been trying for an hour or so, and I can't seem to reproduce
>>> bug where mouse/keyboard events stop being sent when switching to/from
>>> 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
>>> aware of with this release, but I need some help to actually reproduce
>>> 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
>>> the 1.6 server shipped.
>>> I'll be building a bunch of "drop in" server binaries for testing if I
>>> actually reproduce this myself.
>>> Xquartz-dev mailing list
>>> Xquartz-dev at lists.macosforge.org
>> Xquartz-dev mailing list
>> Xquartz-dev at lists.macosforge.org
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
More information about the Xquartz-dev