Mac – Is the MacPort version of XQuartz severly outdated or what

macportssshx11xquartz

At https://www.xquartz.org/ the current version of XQuartz is listed as 2.7.11 but in MacPort it looks like this

$ port search xquartz
xorg-server @1.20.5 (x11, devel)
    The X.org / Xquartz X server.

xorg-server-1.18 @1.18.4 (x11, devel)
    The X.org / Xquartz X server.

xorg-server-devel @1.20.4 (x11, devel)
    The X.org / Xquartz X server.

Found 3 ports.

The xquartz.org version is released 2016 so it is not like MP haven't had time to update. Am I missing something? Exactly what should I install if I want to run X11-applications using a SSH tunnel?

Best Answer

XQuartz is itself dated but is the latest version and works well on High Sierra. The latest version is 2.7.11 dated several years ago. The XQuartz homepage is here. It can be loaded from the link. This latest? version should do what you want.

Related Solutions

Gtk2 randomly crashes

This seems actually to just be a result of my poor programming. I was trying to perform drawing from a thread which was not the same thread that called Gtk_Main, resulting in undefined behaviour and the various error messages above.

MacOS – Xquartz on Mavericks 10.9 fails

/Applications/Utilities/XQuartz.app/Contents/MacOS/X11 is just a shell script that executes whatever is defined as $SHELL in your environment:

case $(basename "${SHELL}") in
    bash)          exec -l "${SHELL}" --login -c 'exec "${@}"' - "${@}" ;;

(etc).

In your case, it look as though $SHELL is set to /usr/local/bin/bash, which doesn't exist. What's interesting, though, is that since you have a prompt at which you have typed xquartz, you clearly are running a shell of some description. However, it doesn't correspond to the value of $SHELL.

Two suggestions for how this might happen:

$SHELL will normally reflect the login shell for your user. You can set that in System Preferences -> Users & Groups -> right click on your username and choose "Advanced Options". If you set this to an invalid value, you won't normally be able to open a terminal... unless you go into the Terminal.app preferences and set the "Shells open with:" option to something which does exist. You'll then get a working terminal with a non-existent $SHELL.
Alternatively, it might be something in your shell startup scripts (.bashrc, .profile, etc) which export a misleading value of $SHELL to the environment. If you have customized any of these, take a look and make sure you're not setting things up incorrectly.

Best Answer

Related Solutions

Gtk2 randomly crashes

MacOS – Xquartz on Mavericks 10.9 fails

Related Question