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

2.3.1_rc3
by Jeremy Huddleston 03 Sep '08

03 Sep '08

Hi all, I'd like to announce another (hopefully the last) rc for 2.3.1. Changes in rc3 over rc1 include: fixed the SwitchCoreKeyboard crash fixes key-equivalents for the input menu (command-space) pulls in Mesa-7.1 for libGLU, libglut, and libGLw uses Mesa-7.0.4 to build the server Please test it out. http://static.macosforge.org/xquartz/downloads/X11-2.3.1_rc3.pkg Thanks, Jeremy

7 14

Environment passed to Applications-launched processes
by Brian Bender 02 Sep '08

02 Sep '08

Hi Jeremy, I wouldn't say it's worth holding up the release process, but I noticed something about the latest prereleases and environment variables -- X11.app doesn't seem to be inheriting the same environment as other Aqua apps (or it's at least not passing it to processes it starts from the Applications menu). I have a couple of shell scripts as entries in X11's Application menu, and they don't work any more (they launch programs that are in /usr/local/bin). I dumped the environment to a file from one script, and it's very bare, PATH only includes "/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin". From my /etc/paths and /etc/paths.d, it should also have "/usr/local/bin:/usr/local/sbin:$HOME/bin:/Developer/Tools:/opt/local/bin:/opt/local/sbin". I'm not sure how far back, but it did pass the full Aqua environment fairly recently. -- Brian

3 6

Application menu no longer customizable
by Martin Costabel 30 Aug '08

30 Aug '08

Since at least 2.3.1-rc2 (but it may have started earlier), I cannot use the "Customize..." facility of the Applications menu in X11.app any more. That is, if I choose "Customize...", the form comes up and I can add new commands in the form or change existing commands, but they do not appear in the Applications menu. I can add entries via "defaults write org.x.X11 apps_menu -array-add '...'", and they show up, although then the default entries disappear, but modification from inside X11.app is impossible. Is this a known bug? -- Martin

3 3

2.3.1rc2 and libGLw
by Jack Howarth 30 Aug '08

30 Aug '08

The change to reintroduce the libGLw.dylib seems like a rather bad idea. Ben Byer told me when Leopard was released that Apple decided to depreciate the libGLw support because Motif itself wasn't shipped with X11. To solve this, I created a mesa-libglw fink package with variants to provide libGLw libraries built against each of the possible Motif's (lesstif, openmotif3...which is 2.2.4 and openmotif4...which is 2.3.0). These are also explicitly linked against the Motif library that is used. Since the Motif headers used to build libGLw vary in the exact symbols that are defined, it is very bad form to try to use a single libGLw for all possible Motif libraries that could be linked into a program. Jack http://pdb.finkproject.org/pdb/browse.php?summary=mesa-libglw

2 1

2.3.1_rc2
by Jeremy Huddleston 30 Aug '08

30 Aug '08

I'd like to announce 2.3.1_rc2 as ready for testing. I've changed a few things since rc1, so I want to run it by you all on xquartz-dev before I announce it to x11-users. Changes over 2.3.1_rc1: # I bumped the version of mesa used to build the server from 7.0.3 to 7.0.4 # I bumped the version of mesa used for libGLU, libglut, libOSMesa, glxgears, and glxinfo to 7.1-rc4 # I'm now shipping libGLw.dylib as well # Fixed a possible crash in SwitchCoreKeyboard resulting from the use of tablets (or anything sending NSTabletPoint events) # Made the delay before adding the launchd socket 3 seconds instead of 2 (xinitrc race kludge) # Added appkit_modifiers defaults option which users can set to 'rcommand' to get access to the input menu with right command (for example) ^^^ This is the best I can do for now for people wanting command- space input menu support. # Added window_item_modifiers defaults item (and option to localization) to change the modifier keys used for the windows menu. ^^^ This is a localization issue... Apparently french users like using command-alt-1 instead of command-1 to choose the first window. go figure. I also added debugging info for the NewCurrentScreen crash, so this will hopefully get that debugging code "out there" more, so someone might actually trigger the bug and be able to hand me something useful to fix it with. If I get no complaints about this, I'll announce it to x11-users Wednesday. http://static.macosforge.org/xquartz/downloads/X11-2.3.1_rc2.pkg Thanks, Jeremy

2 7

1.4.2-apple13
by Jeremy Huddleston 30 Aug '08

30 Aug '08

For those of you wanting to take screenshots, this fixes that bug. ;) I also put debugging information into the reported crash log since people have been reporting crashes and not following up when I ask for the debug information in system.log... so now it should appear in the crash log itself. http://static.macosforge.org/xquartz/downloads/X11-1.4.2-apple13.bz2 --Jeremy

1 0

Where is the VT Fonts pop up on Xquartz 2.2.3?
by J. M. (Jay) Feuillet 30 Aug '08

30 Aug '08

I'm using the latest Xquartz 2.2.3 on Leopard. On my recently purchased 24-inch iMac with the Apple wireless keyboard, when I click in an X-window the Control key, the Main Options pop up. According to my manual Mac OS X for Unix Geeks, if I click Control+Command, the VT Fonts window should pop up. It doesn't. In that window, I should be able to choose fonts like Huge, Large or Medium. On my MBA though, the VT Fonts window pops up and I can choose a bigger font. On both keyboards, the MBA and the iMac, I selected in X11 Preferences "Emulate 3-button mouse", and unchecked "Follow system keyboard layout". Is there another way to get the VT Fonts pop up window to work on the iMac wireless keyboard? Thanks for your help. Jay Feuillet

2 1

Re: [Xquartz-dev] 2.3.1_rc3
by Jeremy Huddleston 29 Aug '08

29 Aug '08

Jack, There is no subscription to process. You just sign up on your own. On Aug 29, 2008, at 16:47, Jack Howarth wrote: > On Fri, Aug 29, 2008 at 11:34:09AM -0700, Jeremy Huddleston wrote: >> >> On Aug 29, 2008, at 06:42, Jack Howarth wrote: >> >>> Jeremy, >>> My previous posting to the xquartz-dev list seems to have >>> gotten lost. Why exactly are you reintroducing libGLw back into >>> X11 on Leopard? I thought Apple explicitly removed libGLw >>> from X11 because they don't ship Motif. >> >> I decided to ship a version of libGLw that doesn't depend on Motif to >> satisfy those of you who were negatively affected by the lack of >> libGLw >> before. >> >> I would actually prefer not to ship it because I don't want to >> really be >> responsible for it, but it build in Mesa-7.1, and I remembered some >> people complaining about it being gone, so I decided to throw it into >> the rc and see if the fish bit. ;) >> >>> On fink, I have >>> created mesa-libglw packages using variants for lesstif, >>> openmotif3 and openmotif4. Since the headers used from >>> Motif by libGLw are not identical across the various motif >>> releases, Apple's original decision to depreciate out >>> libGLw was technically correct.You might want to rethink >>> the decision to reintroduce libGLw back into X11 on Leopard. >>> Jack >> >> This hasn't been shipped final yet (it's only in this RC). I'll >> pretty >> much leave it up to you all here in xquartz-dev... so if anyone has a >> reason to keep it in, speak up... otherwise it gets the boot for >> good. >> >> --Jeremy >> > > Jeremy, > I sent any email about this to xquartz-dev but no one has > ever processed my mailing list subscription so all my emails > are held for review. Can you fix that? > Jack

1 0

Re: [Xquartz-dev] 2.3.1_rc3
by Adam D. I. Kramer 29 Aug '08

29 Aug '08

Command-C and command-Q work fine for me after the _rc3 upgrade., just as they did before the upgrade. Command-V, of course, never worked. =) --Adam On Fri, 29 Aug 2008, Timothy Goins wrote: > Having successfully installed 2.3.1_rc3 (OS X 10.5.4 on a MacPro Intel > machine, 5 GB memory, NVIDIA QUADRO FX 4500 card), I notice that under > X11-Preferences-Output the "Full screen mode" option is not pickable, i.e. > grayed out. This may be something that's been around for a while, since I > have not recently had the need to run in "Full screen mode", which I used to > do on a second monitor (a flat screen TV). I call a rather generic .xinitrc > located in $HOME and see no keyboard mappings that would influence anything > in an OS X Preference pane. > > I also note that Command-Q does not work even with "Enable key equivalents > under X11" selected in X11-Preferences-Input. > > Probably I'm being dumb about something but am curious about what I'm > missing. > > tsg > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (X11-users(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/x11-users/adik-applex11%40ilovebacon… > > This email sent to adik-applex11(a)ilovebacon.org

2 1

Xquartz 2.3.1 RC3 - Crashes
by Marko Oette 29 Aug '08

29 Aug '08

My X11 crashes when used with WINE 1.1.3. (XQuartz 2.3.1 RC3 crashes; 2.3.0 Stable does not) Simply creating windows seems to cause this issue. I'v submitted the bug to apple and attached it to this mail. Greetings, Marko 2008/8/29 <xquartz-dev-request(a)lists.macosforge.org> > > > Message: 2 > Date: Thu, 28 Aug 2008 22:53:31 -0700 > From: Jeremy Huddleston <jeremyhu(a)apple.com> > Subject: [Xquartz-dev] 2.3.1_rc3 > To: "x11-users(a)lists.apple.com Users' List" > <x11-users(a)lists.apple.com>, Developer talk about Xquartz > <xquartz-dev(a)lists.macosforge.org> > Message-ID: <EA37FBAC-CC26-4063-9038-B4725B35AC20(a)apple.com> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > I'd like to announce another (hopefully the last) rc for 2.3.1. > Changes in rc3 over rc1 include: > > fixed the SwitchCoreKeyboard crash > fixes key-equivalents for the input menu (command-space) > pulls in Mesa-7.1 for libGLU, libglut, and libGLw > uses Mesa-7.0.4 to build the server > > Please test it out. > > http://static.macosforge.org/xquartz/downloads/X11-2.3.1_rc3.pkg > > Thanks, > Jeremy > > >

2 1