XQuartz and DISPLAY variable

Not sure what to suggest - I just checked on my installation and I do get a result for "echo $DISPLAY", referring to what looks like a unix socket at (currently) /tmp/launch-31NZS8/org.macosforge.xquartz:0.

I also tried launching Wireshark from the terminal. The first time I got a dialog asking where X11 was located, but after I pointed it at XQuartz everything worked without a problem.

Have you tried running "launchctl list | grep xquartz" to see if the XQuartz User Launch Agent is actually running? Perhaps that's the problem.

DISPLAY only usually gets set by default when you're in an xterm or other X application.

That's the way the older X Window Server X11.app stuff worked on Lion and prior releases, too.

You won't find that opening Terminal.app will typically get DISPLAY set, for instance.

If you're seeing DISPLAY in a Terminal.app session on one system (but not on another), then check whatever shell scripts are being used to log into bash, and compare those with the system that isn't getting DISPLAY set. (That's usually the ~/.bash_profile, ~/.bash_login, and ~/.profile scripts, and only one usually gets executed. For grins, also check the /etc/profile script, but I'd tend to assume the changes weren't there.) See if, for instance, the XQuartz installation modified one of those scripts, and you're not using that script (but some other login script) in one of your two environments.

You won't find that opening Terminal.app will typically get DISPLAY set, for instance.

I think with Leopard, Mac OS X always provided a DISPLAY environment variable, and if something used DISPLAY's contents, X11 would be automatically be started.

Setting DISPLAY in a shell initialization file often messed up X11 on Mac OS X from Leopard onwards.

HOWEVER, I do not have any Mountain Lion experience (yet - I'm going to have to see about downloading a copy and maybe giving it a spin via VMware Fusion 🙂 -- I do have a flash drive on order so I can have a saved local copy of Mountain Lion installer).

When you install Xquartz, log out, and log in again, it will, forever after, set the $DISPLAY variable automatically for you, as long as you don't try to set it manually somewhere in your shell initialization.

It should look something like the following:

zsh-% print $DISPLAY

/tmp/launch-vcKJJv/org.macosforge.xquartz:0

So my guess is that there is something clobbering the $DISPLAY.

Try changing your shell, and see if it works (if you have bash, for example, try switching to zsh with chsh -s /bin/zsh ). In the unlikely event you would want to switch back from zsh, you can just run the same command for /bin/bash

So like he said, something must be clobbering the $DISPLAY variable. Or the launchd job isn't running. For what it's worth, I've just confirmed that the socket is supposed to be launched by a User Launch Agent named org.macosforge.xquart.startx, with the following contents:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>EnableTransactions</key>

<true/>

<key>Label</key>

<string>org.macosforge.xquartz.startx</string>

<key>ProgramArguments</key>

<array>

<string>/opt/X11/lib/X11/xinit/launchd_startx</string>

<string>/opt/X11/bin/startx</string>

<string>--</string>

<string>/opt/X11/bin/Xquartz</string>

</array>

<key>ServiceIPC</key>

<true/>

<key>Sockets</key>

<dict>

<key>org.macosforge.xquartz:0</key>

<dict>

<key>SecureSocketWithKey</key>

<string>DISPLAY</string>

</dict>

</dict>

</dict>

</plist>

So I think the troubleshooting steps should be:

Confirm you have the Launch Agent in the correct location (/Library/LaunchAgents/org.macosforge.xquartz.startx.plist);

Determine if launchd is running the job (ie, are permissions correct, etc, etc);

If so, is the job completing successfully (ie, is there a socket at some point);

If so, when is the socket getting clobbered?

Of course, if it's something in your shell profile clobbering $DISPLAY, then it may be a bit tricky to check the first two without opening a shell...but not impossible.

Yeah; my bad; it's not DISPLAY, it's starting up the X server (before the connection arrives) that makes it easiest to launch the ssh -Y from the xterm in my sequences.

You might want to ask over on the Apple X11 mailing list.

Again, try changing your shell, or, alternatively, create a new test account, and see if it works from that. If so, you know it is something in your own account's configuration files.

I am having the same problem and it looks like the problem is in userspace, because everything is correct under new user. Now I am just at loss here, how to correct things under current user, because the most obvious things like .bashrc, .bash_profile, .profile are all checked through and even thrashed once without any result.

It looks like moving my stuff under new user could be smarter move...

What does your DISPLAY environment variable look like:

echo $DISPLAY

Does it look something like this:

/tmp/launch-egVRmr/org.x:0

The important thing being does it start with /tmp and end in colon 0 (I can't actually type : 0 as adjacent characters, as the forum thinks I'm putting in a smilie 😁 )

AND does the file exist in /tmp/mumble/somthing ?

If not, then you might also check if you created a $HOME/.MacOSX/environment.plist which is another way to customize the user's environment (EXCEPT on Mountain Lion where this has been discontinued).

Is ssh involved? In that .ssh/config can have setup information, which can affect logging into remote systems.

Are you having the problem connecting to a remote system and exporting your display back to the Mac? That could possibily be an issue with the remote system's shell initialization files.

Can you give us more information to work with?

It looks like it should under new user ("/tmp/launch-egVRmr/org.x:0"-ish), but under my current user I get only an empty line as answer to echo $DISPLAY.

Switching the shell to zshell does not change anything - still the same empty line.

When I am logged in as new user, wireshark and other X11 applications will bring XQuartz up and everything works as it should.

On my current user there is no way to bring XQuartz up by other application and when this is tried from command line, then only answer is "cannot open display".

Removing and reinstalling XQuartz does nothing - which is obvious, because the problem does not seem to be on system level.

I have been trying to compare the files in LaunchAgents and other possible places between my current user and new one and have not find anything helpful.

I have not been logging into remote systems lately so I cannot say anything about that. Current user does not seem to have .ssh_config file and system-level ssh_config has XAuthLocation line added by XQuartz.

I do not have anything in $HOME/.MacOSX/ folder. No custom xinit files either.Have macports installed, but not X11 from there.

Wineskin Winery is installed and wineskin apps work without problem.

It seems like posts cannot be edited here after some (not very long) timeout so I have to add this here - there is no org.x:0 file anywhere in /tmp either.

Try these two in the Terminal

[2] local $ grep DISPLAY ~/.*rc ~/.login ~/.*profile ~/.MacOSX/environment.plist 2>/dev/null

[3] local $ grep -r DISPLAY /opt/local/etc /sw/etc /etc 2>/dev/null

If either outputs anything that's were the DISPLAY varaiable is getting stepped on.