Re: announcing Xquartz release 1.2a9
Re: announcing Xquartz release 1.2a9
- Subject: Re: announcing Xquartz release 1.2a9
- From: Brian Campbell <email@hidden>
- Date: Tue, 13 Nov 2007 17:08:10 -0500
On Nov 13, 2007, at 4:44 PM, Ben Byer wrote:
On Nov 13, 2007, at 8:45 AM, Jamie Kennea wrote:
On Nov 13, 2007, at 10:49 AM, Stefan Haller wrote:
* The "stuck modifier key" (shift, command, etc) bug has been
fixed,
again, and hopefully for good.
Hmm, it's still not working for me. It's very easy to reproduce:
open
an xterm, hold down some modifier while clicking on another
application;
release the modifier; bring X11 to the foreground again; the
modifier is
stuck. Always.
Yes, I see the same thing. :(
I'm certainly not trying to insult anyone's intelligence here, but
you did make sure you copied the new binary over the old one ('md5 /
usr/X11/bin/Xquartz' should be 1ec3c29ec0450a2e245dce35291b1bec) and
you completely exited X11.app and restarted it, right?
I quit X11, installed Xquartz-1.2a9, then typed xterm in a terminal. I
confirmed that the problem was still there. Then I saw this email, so
I checked the md5 of the binary, and sure enough, you're right, it's
not 1ec3c29ec0450a2e245dce35291b1bec, instead it was
943707a9ee3b49493f7ebee8c1f81a7e. But I was sure I had installed it.
So I quit X11 again, installed it, checked that the md5, and got
1ec3c29ec0450a2e245dce35291b1bec. Then I launched X, checked the md5
again, and it's 943707a9ee3b49493f7ebee8c1f81a7e. I checked this
against 1.2a8 and the Xquartz that shipped with Leopard, and none of
them match. So now I'm not sure at all what's going on.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden