July 2008 - Xquartz-dev - lists.macosforge.org

2.3.0 not playing well with spaces hot-key combination (locking control key)
by Darren Nickerson 05 Aug '08

05 Aug '08

Folks, I just updated my 10.5.4 box to X11-2.3.0 and I'm experiencing a rather annoying issue. I use a hotkey combination (CTRL + arrow keys) to move around between spaces. When I use this combination to switch out of the space where X11 is runninig, whenever I return to that space (either by hotkeys or using the spaces dock icon) all of my xterms seem to think the CTRL key is still held down. If I press the CTRL key and release it after coming into the X11 space the problem seems to clear itself. I do not see this problem if I use the dock to move out of this space and use a hot-key to come back in. I do not see this problem if I use the dock to move out of this space and use the dock to come back in. I only see this problem if I switch out of this space using the CTRL +arrow hot key combination. Is this a known issue? -Darren

4 9

libSM versions in tiger vs. leopard
by Paul Davis 29 Jul '08

29 Jul '08

it appears that leopard (and all later versions of XQuartz) have moved from libSM v6 (as it was in tiger) to libSM v7. this appears to mean that its either rather difficult or impossible to build an X11 binary for both platforms. is my understand correct? --p

3 4

Announcement: XQuartz 2.3.0 Released
by Jeremy Huddleston 22 Jul '08

22 Jul '08

I'd like to announce the availability of a new release of X11 for OSX Leopard. Version 2.3.0 is now available, and full release notes can be found here: http://xquartz.macosforge.org/trac/wiki/X112.3.0 This version brings in a major update to the server. The server startup model has been reengineered to be more consistent with the OSX application paradigm while also allowing unix X11 applications to get what they expect. Much of the code surrounding the division of labor across the threads in the X11 server has been audited and reengineered to be more stable. Thank you very much to everyone who has helped out in testing release candidates for this release over the past two months. This has been a long road, and I am very appreciative of all the feedback and reports I've gotten along the way.

4 6

2.3.0-rc7 (possibly final)
by Jeremy Huddleston 22 Jul '08

22 Jul '08

Ok, I have a new rc which fixes the last regression I know about (the "Client that triggers launchd to start X11 fails to connect" bug). Please test it out and let me know if there are any other issues that should prevent me from releasing this as 2.3.0. Thanks, Jeremy http://static.macosforge.org/xquartz/downloads/X11-2.3.0_rc7.pkg

6 11

Fullscreen in rootless mode
by Bob 22 Jul '08

22 Jul '08

I'm not sure if this has been discussed before on this list but I don't remember seeing it. It would be really nice to have true fullscreen in rootless mode. This is different than rooted fullscreen support (which would also be great) and so could be implemented faster. What I mean is for a window to be able to cover the entire screen (including mac menu bar and dock) in rootless mode. For example, eye of gnome (eog) has a fullscreen mode that in linux makes it cover the entire screen including the gnome panels (i.e., menus, window switcher, etc). When eog fullscreen is used on mac in rootless mode it covers most of the screen but not the menu bar. I'm not sitting at my leopard machine so I cannot remember what it does with the dock when not hidden, but I know if the dock is hidden then it correctly uses all the space to the bottom of the window. The behavior of covering the menu bar and dock is exactly what many Mac OS X applications do when in "fullscreen" mode. For example iPhoto, Dvd Player, and iMovie to name a few. Why shouldn't X11 applications have the same behavior. Is X11 a 2nd class citizen? I realize that this request is different than what people usually mean but X11 fullscreen (i.e., X11 rooted mode), but it would be great to have both and their implementation would likely be different. I've added this request to the fullscreen bug report on the wiki but thought I would mention it here as well to see what everyone thought.

3 3

2.3.0-rc5
by Jeremy Huddleston 17 Jul '08

17 Jul '08

I'd like to let you all know about another release candidate for 2.3.0: http://static.macosforge.org/xquartz/downloads/X11-2.3.0_rc5.pkg This addresses the remaining regressions that I'm aware of over 2.2.3 and the version in OSX 10.5.2 and later: The main ones I can remember off the top of my head are: issues resulting from spaces in home directory crash on startup a memory leak in pixman no longer shipping libtool archive files /usr/X11/lib/*.la Please test it out and let me know how it works for you... this should probably be release quality, so hopefully I can announce it in the coming week. Thanks, Jeremy

7 23

programs that trigger new X11 launch don't get settings from xrdb
by Lee Aylward 10 Jul '08

10 Jul '08

Hi, I apologize if this has been discussed before, but I was unable to find any significant mention of it. I have a number of urxvt settings in .Xresources which are ignored because launchd runs xinit after urxvt is started. I did see one solution of making a shell script to run xrdb and then urxvt [1], but this does not seem like a great solution as it would have to be done for every application that has a xrdb entry. I can't think of any clean solution, but I do think it is a problem that merits some thought. Thanks, -- Lee Aylward 1. http://lists.apple.com/archives/x11-users/2007/Nov/msg00987.html

1 0

freezing keyboard
by John Koren 01 Jul '08

01 Jul '08

I have found that when I press the option or command keys and at the same time click at X11.app menubar items, my keyboard freezes. Strangely, I am able to get the keyboard working again by pressing twice the numeric lock button. I wonder if others are seeing this behavior. I am using Powerbook G4 (Aluminum) with Mac OS 10.5.3, X11 2.3.0-rc4, X11-1.4.2-apple2, and Xquartz-1.4.2-apple2. Cheers -John

3 8

spaces in pathnames
by Jeremy Huddleston 01 Jul '08

01 Jul '08

So I just pushed a patch to xinit that addresses some issues with spaces in pathnames. One issue remains, and I'm not sure if there's a clean way to address it. At first, I thought I could do something like this: - serverargs=${serverargs}" -auth "${xserverauthfile} + serverargs=${serverargs}" -auth '"${xserverauthfile}"'" but that doesn't work. example: $ mya="Some thing with spaces" $ myargs="1 2 '$mya'" $ ./printargs $myargs argv[0] = ./printargs argv[1] = 1 argv[2] = 2 argv[3] = 'Some argv[4] = thing argv[5] = with argv[6] = spaces' So... any thoughts on how to overcome this cleanly? And no, telling people to not use spaces is unfortunately not an option... and neither is hitting them over the head with a do-better stick. --Jeremy

2 4