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

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

22 Mar '11

John B. Brown wrote: > How does MacPorts install with it's path corrections if you have no .profile or > .bash_profile? What you set in your $HOME is what sets your actually running > environment. Why would you not use your own environment setup instead of some > one size fits all Apple offering? I am not using MacPorts or Fink. I have never needed to. My apps are installed in /usr/local and I have never noticed a problem. If MacPorts or Fink are making "corrections" to fix this problem, I want to learn how to replicate those fixes in a non-MacPorts environment, and document it. I am not attached in any way to the Apple /etc/profile. I just never knew there was an problem with it (and still not convinced there is.) MacPorts and Fink are not required to use XQuartz. I am trying to keep changes to the bare minimum needed. David

3 3

OS X 10.6.7
by Brian Bender 22 Mar '11

22 Mar '11

Hi all, The 10.6.7 update last night supposedly fixed X11 bugs. Should I reinstall the XQuartz-2.6.1 package over top of it now, or leave it alone? Thanks, - Brian

3 3

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

22 Mar '11

> On Mar 21, 2011, at 17:29, Jordan K. Hubbard wrote: >> On Mar 21, 2011, at 5:11 PM, Jeremy Huddleston wrote: >> >>> I think the problem is that you are setting the values in .bashrc. X11 inherits your *login* shell environment. This is set by .profile (not .bashrc). >> >> Actually, for bash, the login shell reads .bash_profile (and only that file - you need to explicitly load your .bashrc from within that file if you want it). > > Well it reads .profile if .bash_profile and .bash_login are absent ... unless in posix mode. For anyone caring, there is a book written on this topic in the INVOCATION section of bash(1), but here's a snippet: > > When bash is invoked as an interactive login shell, or as a non-inter- > active shell with the --login option, it first reads and executes com- > mands from the file /etc/profile, if that file exists. After reading > that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, > in that order, and reads and executes commands from the first one that > exists and is readable. The --noprofile option may be used when the > shell is started to inhibit this behavior. I am still stumped about this. I understand everything you are describing. My $SHELL is /bin/bash. The /etc/profile installed by Snow Leopard looks like this: # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi if [ "${BASH-no}" != "no" ]; then [ -r /etc/bashrc ] && . /etc/bashrc fi BUT My /etc/bashrc contains: export PATH="/usr/local/bin:/usr/local/sbin:/sbin:/bin:/usr/bin:/usr/sbin:/opt/X11/bin:/usr/local/mysql/bin:/usr/local/git/bin:/usr/libexec:." If I open an Apple terminal, then: > echo $PATH /usr/local/bin:/usr/local/sbin:/sbin:/bin:/usr/bin:/usr/sbin:/opt/X11/bin:/usr/local/mysql/bin:/usr/local/git/bin:/usr/libexec:. If I edit ~/.xinitrc.d/99-wm.sh to run just an xterm, with no window manager, then in that xterm: > echo $PATH /opt/X11/bin:/usr/bin:/bin:/usr/sbin:/sbin That is the problem. I don't have user-level files ~/.profile, ~/.bash_profile, or ~/.bash_login since I'm the only user of my laptop. But I shouldn't need to, if the shell is reading /etc/bashrc. When I copy /etc/bashrc to ~/.profile, etc, nothing changes. It is a launchd issue I think. Dave

2 1

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

22 Mar '11

>On Mar 21, 2011, at 17:29, Jordan K. Hubbard wrote: >> On Mar 21, 2011, at 5:11 PM, Jeremy Huddleston wrote: >> >>> I think the problem is that you are setting the values in .bashrc. X11 inherits your *login* shell environment. This is set by .profile (not .bashrc). >> >> Actually, for bash, the login shell reads .bash_profile (and only that file - you need to explicitly load your .bashrc from within that file if you want it). > >Well it reads .profile if .bash_profile and .bash_login are absent ... unless in posix mode. For anyone caring, there is a book written on this topic in the INVOCATION section of bash(1), but here's a snippet: > > When bash is invoked as an interactive login shell, or as a non-inter- > active shell with the --login option, it first reads and executes com- > mands from the file /etc/profile, if that file exists. After reading > that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, > in that order, and reads and executes commands from the first one that > exists and is readable. The --noprofile option may be used when the > shell is started to inhibit this behavior. Thanks. That's an easy enough fix. But I'm a bit confused, because my login shell *is* /bin/bash, and I have always used /etc/bashrc to control my shell environment. The Apple terminal and X11 terminals all open with the environment from /etc/bashrc. So I am surprised to see X11 is different. Should it be different?

1 0

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

21 Mar '11

If I launch XQuartz with "startx" at the terminal, my window manager inherits env variables from my /etc/bashrc If I launch XQuartz by clicking the XQuartz icon, or from the Dock, or by launching an app that invokes X11, the window manager has different env variables passed than from /etc/bashrc. Among other things, PATH is missing /usr/local/bin which is causing things to fail. I changed my .xinitrc to just run xterm, without a wm, and I ran 'env' within that xterm. The env variables were not from /etc/bashrc, and PATH is missing /usr/local/bin. Seems like launchd is not passing my env variables from /etc/bashrc. Docs say that launchd should pass them. Maybe there is a problem with my config, but I don't know where to look. I haven't modified anything in XQuartz. Suggestions?

1 0

XQuartz 2.6.1
by Jeremy Huddleston 18 Mar '11

18 Mar '11

I'm pleased to announce the release of XQuartz-2.6.1. This version pulls in bug fixes for both server and client side issues including RandR crashes, incorrect color profiles (xterms appearing the wrong color), and deadlocks in Xlib with the new xcb transport. libX11 also got a bunch of code cleanup courtesy of some static analysis tools, so we should see some memory leaks disappear and hopefully be more stable in general. Full release notes can be found on the wiki here: http://xquartz.macosforge.org/trac/wiki/X112.6.1 You can download and install using the links below or just check for updates from within X11. As a reminder, this is the last planned release for Leopard. Thanks, Jeremy Leopard: http://xquartz.macosforge.org/downloads/Leopard/X11-2.6.1.dmg SL: http://xquartz.macosforge.org/downloads/SL/XQuartz-2.6.1.dmg

1 0

Re: [Xquartz-dev] Strange Xlib error with e17
by Dave Ray 10 Mar '11

10 Mar '11

Regard the question I just posted about libXp.6.dylib, it appears that is no longer needed. After I recompiled all the prerequisite libs for my app, the app no longer looks for that. So I think it is resolved. Thanks again for the help with the e17 app. Dave

1 0

XQuartz 2.6.1_rc1 - macbook air
by Christof Wolf 10 Mar '11

10 Mar '11

Jeremy, I just installed 2.6.1 rc1 on my macbook air - everything looks fine and is working :-) ciao christof -- public key www.hfph.mwn.de/~chwolf/ch.wolf.asc Please respect my privacy and do not make my contact information available to third parties. This email is UNCLASSIFIED.

2 1

Re: [Xquartz-dev] Strange Xlib error with e17
by Dave Ray 10 Mar '11

10 Mar '11

Thanks again for the help with the e17 app. App developers found a bug in the seek path for X11 libs. Upon fixing, it appears that one of the X11 libs it needs, libXp.6.dylib, is not in /opt/X11, but is in /usr/X11. Would it be a problem to mix that lib from /usr/X11 with others from /opt/X11? Are there plans to include libXp in XQuartz in the future? Dave

2 1

Re: [Xquartz-dev] Strange Xlib error with e17
by Dave Ray 10 Mar '11

10 Mar '11

Thanks Jeremy for the tip. I do see a few libs being loaded from /usr/X11, specifically: dyld: loaded: /usr/X11/lib/libXp.6.dylib dyld: loaded: /usr/X11/lib/libXext.6.dylib dyld: loaded: /usr/X11/lib/libX11.6.dylib dyld: loaded: /usr/X11/lib/libXdmcp.6.dylib dyld: loaded: /usr/X11/lib/libXau.6.dylib The rest are all /opt/X11. Well that would explain it. Full output has 100's of lines: http://pastebin.com/0kbrtben My env has: CFLAGS=-Wall -O2 -arch x86_64 -pipe -I/usr/local/include -I/usr/local/mysql/include -I/opt/X11/include -I/usr/include -I/usr/X11/include LDFLAGS=-arch x86_64 -L/usr/local/lib -L/usr/local/mysql/lib -L/usr/lib -L/opt/X11/lib -L/usr/X11/lib LD_LIBRARY_PATH=/usr/local/lib:/usr/local/mysql/lib:/lib:/usr/lib:/opt/X11/lib:/usr/X11/lib PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/opt/X11/lib/pkgconfig:/opt/X11/share/pkgconfig:/usr/X11/lib/pkgconfig In all of them, /opt/X11 comes before /usr/X11. I am wondering, why is the app using libs in /usr/X11 instead of /opt/X11 when my ENV points to /opt/X11 first? How to I force the app to use /opt/X11, beyond my ENV settings?? There are no crash reports. The app appears to hang, but does not crash or leave a report. If I quit X11 during the hang, the app is still running, and I have to kill -9 it. Dave

3 3