¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

XEphem fails on MacOS 10.15.3 with Macports


 

After upgrading to Catalina, XEphem (installed via Macports) fails at runtime:

% xephem

Building shell

Reading X resources

Checking args

Checking colormap

Building icon

Building main window system

Connecting actions

Building main menu bar

Warning: Fatal Error:

_XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL

Segmentation fault

%

This does not appear to be a Macports problem strictly, as it compiles and installs properly.

?


 

¿ªÔÆÌåÓý

My best guess would be that the Catalina upgrade also upgraded some X11 libs (specifically libXt.6.dylib). I found the following post that while not related directly to XEphem, may provide a solution:

?

?

Alternatively, these two posts also deal with problems with the same library:

?

?

Hopefully that helps?

?

Rick

?

From: SpikeLightfoot
Sent: February 19, 2020 6:35 AM
To: [email protected]
Subject: [xephem] XEphem fails on MacOS 10.15.3 with Macports

?

After upgrading to Catalina, XEphem (installed via Macports) fails at runtime:

% xephem

Building shell

Reading X resources

Checking args

Checking colormap

Building icon

Building main window system

Connecting actions

Building main menu bar

Warning: Fatal Error:

_XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL

Segmentation fault

%

This does not appear to be a Macports problem strictly, as it compiles and installs properly.

?

?


 

Unfortunately these tricks did not work for me. ?Thanks for the suggestions.


 

Don't know what's in Macports but the XEphem.app within my original disk1 ?is statically linked and still works fine on Catalina 10.15.3 with xquartz 2.7.11. One caveat is sometimes it helps to get xquartz running first by running something like xlogo before starting xephem.?


 

Thank you for the pointer. ?I've installed it and indeed it works well. ?Sometimes it's best not to try to solve a bunch of problems all at once!


 

Just to eliminate the obvious, you did reinstall MacPorts, right?


 

Not so obvious to me! ?But I did reinstall and got the same result.


 

MacPorts is MacOS release specific. In general with each release of MacOS, I¡¯ve had to update Xcode, and MacPorts. And as someone else pointed out, you want to make sure your XQuartz is up to date.

Sorry this didn¡¯t fix your problem.


 

I am seeing failure as well; I get the error message: "can't open display" twice; then it quits...

I tried rebuilding it which seemed successful, but same error.

I tried previous suggestions to no avail; I am no OS X guru, so detailed suggestions would be welcome.

Thanks in advance.


 

xephem could stand to have a network of maintainers to help it over
these problems as libraries and operating systems change over time. I
remember in Linux it took some time and fiddling because it uses
xprint (I think it was) which has mostly passed out of common usage.
It would be a fairly thankless job I think, and I'm not much younger
than Elwood. I've never seen OS X, and i don't grok AppleSpeak.

On 2/21/20, David Reed <w5sv.dave@...> wrote:
I am seeing failure as well; I get the error message: "can't open display"
twice; then it quits...

I tried rebuilding it which seemed successful, but same error.

I tried previous suggestions to no avail; I am no OS X guru, so detailed
suggestions would be welcome.

Thanks in advance.



--
-------------
No, I won't call it "climate change", do you have a "reality problem"? - AB1JX
Cities are cages built to contain excess people and keep them from
cluttering up nature.
Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach


 

Have you checked your DISPLAY environment variable? On macOS the old favorite :0 does not work. At the moment mine is:

echo $DISPLAY
DISPLAY=/private/tmp/com.apple.launchd.Y3GlPNjYOH/org.macosforge.xquartz:0

This should be set automatically when you log in when xquartx is started by launchd but if not, try looking in /private/tmp for something similar then set it yourself, for example:

export DISPLAY=/private/tmp/com.apple.launchd.Y3GlPNjYOH/org.macosforge.xquartz:0
xephem

You are running xquartz right? Never use macports x11, that is way out of date, and trying to mix it with xquartz will lead to much grief. Uninstall if you have it then get , or try installing it again anyway in case it is messed up somehow.



 

For what it's worth, for purposes here I don't think MacOS is much different than Linux, since it's BSD-based and there is a nice X11 distribution available to install seamlessly. ?Windows would be different, I think. When we eventually figure this out I don't think it will have turned out to be a big deal. ?Says Mr. Optimism...


 

Thanks for the suggestion, Elwood. ?For me:

% echo $DISPLAY

/private/tmp/com.apple.launchd.nupkkTMJpP/org.macosforge.xquartz:0

%

% xephem

Building shell

Reading X resources

Checking args

Checking colormap

Building icon

Building main window system

Connecting actions

Building main menu bar

Warning: Fatal Error:?

_XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL

Segmentation fault

%?


 

Elwood,

thanks for trying to help. ?Yes, I am running xquartz; this all worked in the previous release. it broke with macOS Catalina 10.15.3

I am thinking to remove it all and rebuild from scratch, but I fear doing that so I hesitate.

I will no doubt kick myself when I get it running for having overlooked the obvious, but meanwhile (well, you get it).


 

Further investigations revealed that it was quartz that was "broken"; reinstalled it and did a fresh installation of the execrable of XEphem, and all is well.
Thanks to all for your help & support.


 

Too many typos; sorry for all that; quartz was failing..reinstalling that and the executable of XEphem fixed it all up.


 

Uninstalling XEphem from Macports, reinstalling XQuartz, and rebuilding XEphem in Macports still failed. ?I downloaded the 3.7.7 source code, installed OpenSSL via MacPorts, applied the two patches in the User Contrib directory, and XEphem built successfully.

I'm thinking something is broken with Macports after all.


 

Other Macports users report the same bug:?
Until the port is fixed XEphem is DOA via Macports, it seems.