[Xquartz-dev] XQuartz 2.6.1_rc1

[Jeremy Huddleston]

On Mar 20, 2011, at 03:46, Peter Dyballa wrote:

>> The MacPorts X server does not set anything as $HOME.
> 
> OK! Instead of at $HOME I land (get logged) in /.

Switch xterm to use login shells to work around this.  Put this in ~/.Xresources:

XTerm*loginShell:	True


>> The startup models of both XQuartz and MacPorts' X11.app are identical.  Chances are you're seeing different behavior because one is going down the launchd path, and the other is not.
> 
> The MacPorts X server is launched by clicking on the icon in Dock, the other is launched (because only rarely used) by 'open /Applications/Utilities/X11.app'. When the MacPorts X server is launched as 'open /Applications/MacPorts/X11.app' it exhibits the same behaviour. Launched as '/Applications/MacPorts/X11.app/Contents/MacOS/X11 &' it's still the same.
> 
> MacPorts uses "X.Org X Server 1.9.3.902", the other one is "X.Org X Server 1.9.4.901". /Applications/Utilities/X11.app (2.6.1_rc1) complains at once about
> 
> 	X11.app: DISPLAY ("/tmp/launch-qJJhvw/org.macports:0") does not match our id ("org.x"), unsetting.

That's expected.  It's then forking and execing startx on its own rather than letting launchd do it.  As mentioned before, this is the source of the difference.  One is using launchd, the other isn't.  It has nothing to do with the actual code os MP's X11.app vs Apple's X11.app.

> and later:
> 
> 	xauth:  file /Users/pete/.serverauth.3176 does not exist
> 	xauth: (stdin):2:  unknown command "50ffffd5feb04442cf3539293f3f38b2"

That is puzzling.  You should investigate that.

> X.Org X Server 1.9.5 from 11.app 2.6.1 behaves the same.

As expected.