xemacs: X server not responding : "/private/tmp/com.apple.launchd.AZMsfJLVjl/org.xquartz:0.0"

[lpagani91]

Hello,

When I start xemacs, it crashes with this message :

X server not responding
: "/private/tmp/com.apple.launchd.AZMsfJLVjl/org.xquartz:0.0"

Context : it was running before but Xquartz froze and I had to kill it. Meanwhile, a few days ago I did a port selfupdate + upgrade outdated but this one stops on a python library which cannot update (py37-pyobjc, #66550). So I cannot finish the upgrade of the ports.

Now I have 16 broken ports :

--->  Found 16 broken files, matching files to ports     
Warning: No port py27-healpy found in the index; can't rebuild
Warning: No port py36-healpy found in the index; can't rebuild
--->  Broken files found, but all associated ports are not in the index and so cannot be rebuilt.

How can I bypass py37-pyobjc upgrade to continue upgrading the rest ? and/or how can I fix the 16 broken files ? I tried to upgrade xemacs directly but it does not help.

Thanks for help

[lpagani91]

forgot to mention I am running on 10.12.6

[ryandesign (Ryan Carsten Schmidt)]

For one thing, you can uninstall py27-healpy and py36-healpy since they have been deleted from our ports collection. I don't know what the 14 other broken ports that you have but the message said they're all not in the index, so they may all be ports that have been deleted, and so you should uninstall them as well.

[ryandesign (Ryan Carsten Schmidt)]

Oh wait, 16 broken files. Belonging to just those two ports. Which have been deleted. So after you uninstall those two ports, there should be no more broken files.

[lpagani91]

OK, I will do that. Thanks for the tips. For the X server not responding, I am in an even worse situation : I upgraded my 10.15 machine for which pyobjc can be built without problems, I had a few minor problems I could solve following the instructions but at the end Xemacs does not work any more just like on the 10.12 machine with the same message X server not responding "/private/tmp/com.apple.launchd.xxxx/org.xquartz:0.0" I am doomed!

[ryandesign (Ryan Carsten Schmidt)]

Well the broken files reported by rev-upgrade likely have nothing to do with the xemacs problem. Maybe that port's maintainer, to whom I'm assigning the ticket now, can help with that. If it is truly crashing, it will have left a crash log in ~/Library/Logs/DiagnosticReports; if so, please attach it; it may give a clue about what's wrong.

[lpagani91]

I agree about the broken files. They have been here for a while...without much problem. By the way did you also remove py37-h5py ? I will look for the crash file now

[lpagani91]

No file from today in the DiagnosticReports Did not find a hint on internet either about this problem.

[lpagani91]

I know it is not easy to reverse to a previous XEmacs version, but should I try this ? In fact, not a good idea because I believe that XEmacs has not been recently updated. It only suffers from a side effect of something else I would say ?

[lpagani91]

X server not responding : "/private/tmp/com.apple.launchd.AZMsfJLVjl/org.xquartz:0.0"

Lorenzo>echo $DISPLAY /private/tmp/com.apple.launchd.AZMsfJLVjl/org.xquartz:0

Is the 0.0 instead of 0 a problem ? I can start Xterm windows as many as I want and applications (not from MacPorts) like ds9 start and open windows alright.

[lpagani91]

Replying to ryandesign:

Oh wait, 16 broken files. Belonging to just those two ports. Which have been deleted. So after you uninstall those two ports, there should be no more broken files.

all cleared, indeed. Thx

[ryandesign (Ryan Carsten Schmidt)]

Replying to lpagani91:

By the way did you also remove py37-h5py ?

According to ​https://ports.macports.org/port/py37-h5py/details/ yes the port was deleted. This happened in baaab3ac94a12d5b32034e388f6987b04ed197d1/macports-ports. It is not uncommon for python module ports for obsolete versions of python to be deleted.

[lpagani91]

I see but this is annoying since I still need python3.6 to run a parallelized code with pyopencl which seems to work only with python3.6. Therefore if these versions of python lose some important libraries (for me, I know) like h5py, I will end up with no version of python where I can work with all my tools.

I alerted two years ago about the pyopencl problem (#63444) but got no reaction. pyopencl has been ported to py3.8, 3.9 and 3.10 by now but it crashes the same in all versions except py3.6.

[lpagani91]

Hello, I still have the Xemacs crashing at start with this message :

X server not responding : "/private/tmp/com.apple.launchd.AZMsfJLVjl/org.xquartz:0.0"

[ryandesign (Ryan Carsten Schmidt)]

Let's retitle this. I'm not seeing any evidence of a crash, I'm only seeing an error message.