October 2009 - Xquartz-dev - lists.macosforge.org

Input Grab (Input on Focus) issue
by Jeremy Huddleston 08 Nov '09

08 Nov '09

So I'm now able to reproduce the issue fairly repeatedly. That doesn't mean the fix will be soon... just that I'm not working on it and will be exploring different possibilities. Thanks to everyone for offering reproduction advice. --Jeremy

8 19

My hack for reading .Xmodmap
by Martin Otte 04 Nov '09

04 Nov '09

Hi, I was doing some experimenting with the latest servers, and found that the only way to get my custom .Xmodmap to be loaded automatically at startup was to force it to be read at the end of the DarwinKeyboardReloadHandler routine. Is it safe to call xmodmap at the end of the DarwinKeyboardReloadHandler routine? Using xmodmap is much easier than trying to parse the .Xmodmap files and then calling XkbApplyMappingChange. I had to background the calls to xmodmap or else the server would hang waiting for the xmodmap processes. I also only call xmodmap on the second (or any subsequent) calls to DarwinKeyboardReloadHandler. Here is my ugly hack to quartzKeyboard.c that seems to be working for me: diff -up xorg-server-1.4.2-apple49/hw/xquartz/quartzKeyboard.c.orig xorg-server-1.4.2-apple49/hw/xquartz/quartzKeyboard.c --- xorg-server-1.4.2-apple49/hw/xquartz/quartzKeyboard.c.orig 2009-10-14 11:06:49.000000000 -0400 +++ xorg-server-1.4.2-apple49/hw/xquartz/quartzKeyboard.c 2009-10-14 00:07:14.000000000 -0400 @@ -172,6 +172,7 @@ const static struct { darwinKeyboardInfo keyInfo; pthread_mutex_t keyInfo_mutex = PTHREAD_MUTEX_INITIALIZER; +int ran_darwin_kbdreload = 0; static void DarwinChangeKeyboardControl(DeviceIntPtr device, KeybdCtrl *ctrl) { // FIXME: to be implemented @@ -372,6 +373,9 @@ void DarwinKeyboardReloadHandler(void) { CFIndex initialKeyRepeatValue, keyRepeatValue; BOOL ok; DeviceIntPtr pDev = darwinKeyboard; + const char *xmodmap = PROJECTROOT "/bin/xmodmap"; + const char *sysmodmap = PROJECTROOT "/lib/X11/xinit/.Xmodmap"; + char *homedir, usermodmap[1024], cmd[1024]; DEBUG_LOG("DarwinKeyboardReloadHandler\n"); @@ -415,6 +419,28 @@ void DarwinKeyboardReloadHandler(void) { } XkbUpdateCoreDescription(darwinKeyboard, 0); } pthread_mutex_unlock(&keyInfo_mutex); + + if (ran_darwin_kbdreload > 0 && access(xmodmap, F_OK) == 0) { + + /* Check for system .Xmodmap */ + if (access(sysmodmap, F_OK) == 0) { + snprintf (cmd, sizeof(cmd), "exec %s %s &", xmodmap, sysmodmap); + System(cmd); + } + + /* Check for user's local .Xmodmap */ + homedir = getenv("HOME"); + if (homedir != NULL) { + snprintf (usermodmap, sizeof(usermodmap), "%s/.Xmodmap", homedir); + if (access(usermodmap, F_OK) == 0) { + snprintf (cmd, sizeof(cmd), "exec %s %s &", xmodmap, usermodmap); + System(cmd); + } + } + + } else + ran_darwin_kbdreload++; + } //----------------------------------------------------------------------------- Thanks, Martin

3 3

MacUpdate Dev: XQuartz updated
by updates＠macupdate.com 30 Oct '09

30 Oct '09

Freedesktop.org, XQuartz 2.4.1a3 has just been updated to version 2.4.1_alpha3 on MacUpdate. Check it out at: http://www.macupdate.com/info.php/id/26593/xquartz Please keep MacUpdate informed of any new Mac version releases of your products, so we can promote them for you. You can update your listing by signing up for a developer tools account: http://www.macupdate.com/developer/ Partner in our 24-hour promotion of your software through mupromo.com: http://www.mupromo.com/ -MacUpdate Team www.macupdate.com [You're being notified of this update because you're listed as the developer of XQuartz. Please email us if you are not the developer: updates(a)macupdate.com]

2 1

2.4.1_alpha1 for SnowLeopard
by Jeremy Huddleston 28 Oct '09

28 Oct '09

So, I finally resolved my build issues. Here's 2.4.1_alpha1 for SnowLeopard. It makes that ptty resize option on by default to workaround the bug in xterm/ptty. It installs in /opt/X11, /Library/Launch*, /Applications/Utilities/ XQuartz.app This release is the first to allow differnt X11 servers to "own" $DISPLAY. You can pick which X11 server will actually "own" it by disabling the others' startx LaunchAgents. You will notice (after logout/login) that $DISPLAY now has "org.macosforge.xquartz" in its filename which identifies XQuartz.app as the owner. That being said, SL's X11 assumes that it owns $DISPLAY. If you run X11.app while it's not the owner, it will actually trigger XQuartz.app to start and wait forever for its own startup notification. Hopefully I can get X11 a SoftwareUpdate in a future dot release of OSX to update this (or you can do it on your own by copying over a new X11.bin into X11.app). X11 servers that don't "own" DISPLAY will unset DISPLAY and their children will continue to use the traditional DISPLAY values (":1", ": 2", etc). I did not update the release notes in the .pkg, so you'll need to check the site for a full changelog: http://xquartz.macosforge.org/trac/wiki/ChangeLog Here's the dmg: http://static.macosforge.org/xquartz/downloads/SL/X11-2.4.1_alpha1.dmg Note: X11 alpha/beta updates will only be released for SL. rcs will be rolled for both Leo and SL. It's just not worth the extra overhead. Thanks, Jeremy

5 9

wm-quarz and alpha 3
by Christof Wolf 28 Oct '09

28 Oct '09

Jeremy, The new wm-quarz and alpha 3 works fine. thanks christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

1 0

configuration
by Christof Wolf 26 Oct '09

26 Oct '09

On Wednesday 21 October 2009, xquartz-dev-request(a)lists.macosforge.org wrote: > Those of you seeing this, let's try to figure out why I'm not > reproducing it. What are your configurations: > > laptop/trackpad? keyboard/mouse? tablet? Jeremy, I can reproduce it on my two macs 1) MacBookPro 2.4 GHz Intel Core 2 Duo, 4GB Ram 667 MHz (US model) GeForce 8600M GT, SL 10.6.1 I think I bought it 1,5 year ago :-) with wacom tablet - latest driver installed, but with or without the tablet - no difference, I don't have an external keyboard 2) MacBook Air 1.86 GHz Intel Core 2 Duo, 2 GB Ram 1067 MHz (US model) NVIDIA GeForce 9400M, SL 10.6.1 - I bought in April this year, but there are newer models after that :-( I have the latest wacom driver installed but often I use it without any additional mouse, tablet etc. but exactly the same behavior like the MacBook Pro Christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

3 4

Re: [Xquartz-dev] Configuration
by Christof Wolf 26 Oct '09

26 Oct '09

> I can reproduce the problem on my MacBook3,1 running 10.6.1 with > Xquartz 2.4.1_alpha3 (with and without X11.bin-1.7.0.901). Doesn't > matter if I use the internal trackpad or the external USB mouse. As > soon as I switch away from X11 the input seems to be frozen and not > being restored when switching back to X11 (that even holds for the > quartz title bar of the X11 windows -- there's no interacting with the > title bar or the three shiny buttons). But I noticed that the input > can be restored if one minimizes (cmd+m) the X11 window and restores > it from the Dock. Could that at all be a problem related to the > WindowServer-X11-brigde instead of X11 itself? Jeremy, I can reproduce exactly the same behavior as Heiko has described it above - X11 can be reactivated after minimizing and restoring it. That works for alpha 2 and 3. ciao christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

1 0

Re: [Xquartz-dev] configuration - shift key does not work
by Christof Wolf 23 Oct '09

23 Oct '09

On Friday 23 October 2009, xquartz-dev-request(a)lists.macosforge.org wrote: > I was actually joking with someone about this earlier... but if > someone experiencing this bug is in the Bay Area and wouldn't mind > showing it to me in person, I'd be willing to come visit you and > hopefully get to the bottom of it... wouldn't that be an excellent excuse for a transatlantic tip :-) another weird thing, with alpha 3 and 1.5.3 if I write an email with Kmail, the shift key does not work, so no capital letters. The only way to get a capital letter is to use caps lock. Interestingly if I open a terminal everything works fine, and it works in the main window of Kmail, e.g. if I use the shift key on the quick search bar, fine. Only if I open a new message window I cannot use the shift keys. Not sure if that is related to our issue. Christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

1 0

frozen keyboard/mouse
by Christof Wolf 20 Oct '09

20 Oct '09

> To summarize, we have confirmation that simply reverting to the alpha1 > server binary fixes the problem. I want to now confirm that it is > indeed a 1.5 to 1.6 regression rather than something that I've been > pushing to both branches. I've built the recent xorg-server binaries > for both 1.5 and 1.6: > > http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.5.3-apple18.bz2 > http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.6.5-apple2.bz2 > > Please try out alpha2 with this 1.5.3-apple18 binary. My hunch is > that it will work, but I want to confirm that before I waste time > looking in the wrong places. Jeremy, I tested alpha 2 and 3 with the same results :-) 1.5.3-apple-18 worked fine, but not 1.6.5-apple2 Christof -- public key www.hfph.mwn.de/~chwolf/chwolf.asc Please respect my privacy and do not make my contact information available to third parties.

4 4

frozen keyboard/mouse
by Jeremy Huddleston 20 Oct '09

20 Oct '09

I still can't get this to reproduce. To summarize, we have confirmation that simply reverting to the alpha1 server binary fixes the problem. I want to now confirm that it is indeed a 1.5 to 1.6 regression rather than something that I've been pushing to both branches. I've built the recent xorg-server binaries for both 1.5 and 1.6: http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.5.3-apple18.bz2 http://static.macosforge.org/xquartz/downloads/SL/X11.bin-1.6.5-apple2.bz2 Please try out alpha2 with this 1.5.3-apple18 binary. My hunch is that it will work, but I want to confirm that before I waste time looking in the wrong places. Thanks, Jeremy

2 1