As some of you are aware, after the release of 2.2.0, I decided to just announce release candidates to the xquartz-dev list and final releases to the x11-users list. With the release of 2.3.0, however, that release candidate process didn't catch some show-stopper issues. As a result, I've decided to announce "betas" to xquartz-dev and "rcs" to x11-users. These "rcs" are what I would've released under the old process (no show stoppers found in the releases announced to the xquartz-dev list), but this gives me an expanded user base to catch additional show stoppers before I announce a final update on the website and macupdate.com. I've just uploaded a release candidate for 2.3.1, and I urge everyone who experienced problems with 2.3.0 to give it a try. The following are the main issues addressed: * X11.app now properly notices button clicks with tablets * Fixed xinitrc / launchd-first-client race condition * Re-added old fallback keyboard map detection fallback with extra debugging * Capslock "press ignored" bug is fixed. * Fixed stuck modifier key bug * Fixed 3-button mouse emulation * The list of modifiers allowed in the fake_button{2,3} defaults has been expanded: o fn,{l,r,}{command,alt,shift,control} package: http://static.macosforge.org/xquartz/downloads/X11-2.3.1_rc1.pkg draft release notes: http://xquartz.macosforge.org/trac/wiki/X112.3.1 Thanks, Jeremy
2.3.1rc1 seems to have indeed squished the "stuck modifiers" bug that was bugging me. I am getting a few occasional weird log entries, though, including: DarwinPressModifierKey bad keycode: key=1469159 DarwinPressModifierKey bad keycode: key=1469153 Any idea what this is, and/or whether it matters?
What keyboard layout are you using? What key are you pressing that is causing that? I'm guessing it might be something like Fn, eject, volume+, or some other "oddball" key. If you could narrow it down, that would help. If you're seeing a delay in the log file with Console.app, you can do what I do to debug. Open up terminal.app with 2 tabs In tab 1, run /Applications/Utilities/X11.app/Contents/MacOS/X11 -- listenonly In tab 2, run xterm tab 1 now shows what would be sent to your system.log. Thanks, Jeremy On Aug 17, 2008, at 21:54, Andrew Farmer wrote:
2.3.1rc1 seems to have indeed squished the "stuck modifiers" bug that was bugging me. I am getting a few occasional weird log entries, though, including:
DarwinPressModifierKey bad keycode: key=1469159 DarwinPressModifierKey bad keycode: key=1469153
Any idea what this is, and/or whether it matters?
On 17 Aug 08, at 22:41, Jeremy Huddleston wrote:
What keyboard layout are you using? What key are you pressing that is causing that?
I'm using bog-standard U.S. layout on a Macbook. The log message actually doesn't seem to be linked with any specific keystroke, oddly enough... I've gotten it to show up a few times, but repeating the keystrokes I was hitting at the time doesn't make it recur.
Hmm... well keep an eye on it and if you can figure out what it is, great... if not, don't worry about it. I'm curious about it, but as long as everything seems to be working right, /shrug... --Jeremy On Aug 17, 2008, at 22:49, Andrew Farmer wrote:
On 17 Aug 08, at 22:41, Jeremy Huddleston wrote:
What keyboard layout are you using? What key are you pressing that is causing that?
I'm using bog-standard U.S. layout on a Macbook. The log message actually doesn't seem to be linked with any specific keystroke, oddly enough... I've gotten it to show up a few times, but repeating the keystrokes I was hitting at the time doesn't make it recur. _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (2)
-
Andrew Farmer
-
Jeremy Huddleston