March 2011 - Xquartz-dev - lists.macosforge.org

2.6.0_beta2
by Jeremy Huddleston 29 Sep '11

29 Sep '11

I just uploaded 2.6.0_beta2 which pulls in all the updates in X11R7.6 RC1 plus the xorg-server 1.9.3 RC1 server. You can obtain the update by checking for updates in the X11 menu or directly here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_beta2.dmg The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog The only XQuartz specific changes I want to address before making rc1 are related to RandR. If you find any regressions or serious issues, please let me know. --Jeremy

3 11

XQuartz 2.6.1_rc1
by Jeremy Huddleston 01 Apr '11

01 Apr '11

I've just uploaded 2.6.1_rc1 for both Leopard and Snow Leopard. This pulls in a few more fixes for RandR and should address the "xterm changes background color" issue that cropped up a few releases ago. There are still a couple RandR related issues that I want to tackle before the final release. Please give it a whirl and let me know if there are any regressions. Thanks, Jeremy http://static.macosforge.org/xquartz/downloads/Leopard/X11-2.6.1_rc1.dmg http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.1_rc1.dmg

3 42

xquartz problem with ros
by John Muccigrosso 26 Mar '11

26 Mar '11

I play around a bit with ros on my macbook and I just upgraded to the new xquartz yesterday (2.6.1). Previously I was just using Apple's X11. No problems with most things (not that I run a lot in X): xterm fires up the xquartz version, for example. But running one of my ros binaries (pcd_viewer) gives me this error: <Error>: unknown error code: invalid pixel format Fri Mar 25 09:40:16 client-6-50-27.bc.drew.lan pcd_viewer[1954] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. X Error of failed request: GLXBadContext Major opcode of failed request: 0 () Serial number of failed request: 39 Current serial number in output stream: 39 If I launch Apple's X11 and get an xterm there (so it's running from /usr instead of /opt), pcd_viewer will launch fine. At least one other ros binary doesn't have a problem with xquartz, so I suspect something in pcd_viewer. echo $DISPLAY from terminal reports: /tmp/launch-2LgGpc/org.macosforge.xquartz:0 from Apple's X11 it reports :1 I'm a bit of a newbie, so I thought I'd ask here first whether there's an obvious problem somewhere that is easily resolved. Thanks. John

2 5

Re: [Xquartz-dev] XQuartz 2.6.1_rc1
by Dave Ray 25 Mar '11

25 Mar '11

Peter Dyballa wrote: > The final release has a strange habit: it launches an extra xterm! How > can I stop it doing so?... I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final seems to reset my plist, it reverted to the default which opens an xterm from launchd. I followed instructions in the user FAQ to make it go away: http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ. You can check if that's whats causing it with: defaults read org.macosforge.xquartz.X11 If needed, you can turn it off with: defaults write org.macosforge.xquartz.X11 app_to_run /usr/bin/true You may have already looked at this, just a thought. Dave

3 9

Re: [Xquartz-dev] env variables and launchd problem
by Dave Ray 24 Mar '11

24 Mar '11

Peter Dyballa wrote: >> I'm not using bash, I'm true to tcsh. It works as described: What I >> set in ~/.login appears in the environment of the X clients. (The >> question stays: Why do I have to set the environment values twice?) >> And X11.app obviously knows the value of $HOME; why doesn't it launch >> its X clients in $HOME? GNU Emacs, FontForge, xterm – all are in /! >> X11.app has PWD=/Users/me. Why do the X clients forget it or set it >> to /? They have HOME=/Users/me set. Actually, a correction. I'm observing the same thing on shells that are launched by my window manager (e17). Those shells are dropping me in at the root level, but my ENV looks correct in those shells. $HOME=/Users/davidray. Shells/terminals launched by X11.app (from the Applications menu) are correctly dropping me into my home directory. It seems there's something unusual about the environment that the wm is getting. I'm using a 3rd party wm so it's hard for me to tell if the issue is in XQuartz or that wm. Dave

3 2

Re: [Xquartz-dev] env variables and launchd problem - solved
by Dave Ray 24 Mar '11

24 Mar '11

Jeremy Huddleston wrote: > > Is there a good way for me to pass my ENV to whatever is launched by ~/.xinitrc.d/99-wm.sh, without passing the ENV to every single launchd process? > > Yes. > > echo ". ~/.profile" > ~/.xinitrc.d/00-env.sh > echo "cd $HOME" >> ~/.xinitrc.d/00-env.sh > chmod 755 ~/.xinitrc.d/00-env.sh That solved everything. Thanks! On unix I always did this, but I never did it on MacOS. It wasn't intuitive that xinit would pass a different ENV than launchd. I suspect this will fix Peter's problem as well. -Dave

1 0

Re: [Xquartz-dev] env variables and launchd problem
by Dave Ray 24 Mar '11

24 Mar '11

Jeremy Huddleston wrote: > > I'm observing the same thing on shells that are launched by my window > manager (e17). Those shells are dropping me in at the root level, but my > ENV looks correct in those shells. $HOME=/Users/davidray. > > > Shells/terminals launched by X11.app (from the Applications menu) are > correctly dropping me into my home directory. > > Ok, this is likely because your WM is launched from xinit which is > launched by launchd which probably has PWD=/ Yes that might explain it. The wm binary I launch in ~/.xinit.d/99-wm.sh is not the actual window manager, it invokes the wm, possibly through xinit. I wonder, would this also explain why an xterm launched from ~/.xinitrc.d/99-wm.sh (with no window manager) does not have the expected ENV? The missing ENV in that xterm correlates with the WM issues. When I add ~/.MacOSX/environment.plist, or /etc/launchd.conf, the problem goes away for whatever I am running in ~/.xinitrc.d/99-wm.sh, whether it be that xterm or a WM. Is there a good way for me to pass my ENV to whatever is launched by ~/.xinitrc.d/99-wm.sh, without passing the ENV to every single launchd process? Dave

2 1

Re: [Xquartz-dev] env variables and launchd problem
by Dave Ray 24 Mar '11

24 Mar '11

On Mar 23, 2011, at 7:00 AM, Peter Dyballa wrote: >>> IMO this should not be necessary, because up to Leopard ~/.MacOSX/ >>> environment.plist is read when you log in. Then all processes >>> inherit this environment. The X clients are a bit different and >>> used to inherit their environment from X11.app ? until recently! >> >> Nope. X11 clients do inherit their environment from X11.app, since >> that's the process that forks and execs them. That has not changed. > > Yes, right! The problem is that X11.app now does not inherit the set > environment and passes something not so useful to the X clients. Which > needs to be corrected. Particularly the manner to set / als current > working directory. $HOME is correct. Thank you Peter for being the first on the list to answer my question, after a zillion posts on the topic. So the problem is not a config issue on my machine, others are seeing it. This helps me enormously. I am also using ~/.MacOSX/environment.plist as a work-around, to make sure the right ENV gets passed to X11 when it is launched by launchd. I agree with Jeremy that it is not the best solution, just the only one available now. That file passes its ENV to every launchd process, where I really only need it to be passed to X11. Dave

4 7

Re: [Xquartz-dev] env variables and launchd problem
by Dave Ray 24 Mar '11

24 Mar '11

Peter Dyballa wrote: > > I'm not using bash, I'm true to tcsh. It works as described: What I > > set in ~/.login appears in the environment of the X clients. (The > > question stays: Why do I have to set the environment values twice?) > > And X11.app obviously knows the value of $HOME; why doesn't it launch > > its X clients in $HOME? GNU Emacs, FontForge, xterm – all are in /! > > X11.app has PWD=/Users/me. Why do the X clients forget it or set it > > to /? They have HOME=/Users/me set. I'm observing the same thing. My shells launched in X11 are dropping me in at the root level. My ENV looks correct in those shells. $HOME=/Users/davidray. Dave

1 0

env variables and launchd problem
by Dave Ray 23 Mar '11

23 Mar '11

I want to ask again because nobody replied to my previous post, and maybe I should provide more info. My environment variables do not seem to be passed to X11 apps when starting up XQuartz with launchd. A different set of env variables are there. I am not sure when this problem started, I only just now discovered it. I launched an xterm from ~/.xinitrc.d/whatever.sh and typed 'env'. I could post the actual values but I don't think it's important. I can fix the problem by adding the appropriate variables to ~/.MacOSX/environment.plist. But then I have two files to maintain, /etc/bashrc and ~/.MacOSX/environment.plist. I would prefer not to have to do that, unless that is the expected way. According to the XQuartz FAQ (http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ) XQuartz should inherit my shell environment, and says I should post to this list of it isn't. I'm using the latest XQuartz 2.6.1 final on Snow Leopard 10.6.6. I have removed /Applications/Utilities/X11.app (actually, compressed it) and renamed /usr/X11 and /usr/X11R6 to /usr/X11-temp and /usr/X11R6-temp. This is to be absolutely sure there aren't conflicts in the two X11 environments. (Is this bad?) The problem happens regardless of what I launch from my ~/.xinitrc.d/whatever.sh. The problem does not occur if I start XQuartz without launchd, for example, by typing 'startx' at the terminal. I looked over my system and don't think it''s a config issue, but if someone confirms the problem is limited only to my machine, I will look further. Could someone chime in and let me know if this is normal or not, my env in /etc/bashrc not being passed to the apps launched from ~/.xinitrc.d/whatever *IF and only IF* they are launched by launchd. Thanks.

4 6