Ticket #337 (closed crash)

Opened 2 years ago

Last modified 2 years ago

XQuartz 2.4.0 problems with Biggles

Reported by: dcn@… Owned by: jeremyhu@…
Priority: Nice to Have Milestone: 2.5.0
Component: xserver Version: 2.4.0 (xserver-1.5.3-apple14)
Keywords: Cc:

Description (last modified by jeremyhu@…) (diff)

Using either a direct install of the graphics program biggles (current version,  http://sourceforge.net/projects/biggles/) or the Macports install of the same, I get the error, triggered by the biggles command plot.show():

Error: Unresolved inheritance operation

When I reinstalled the standard OSX 10.5.8 x11 via the combo update, the error disappeared.

DN

Attachments

xorg-server.txt.zip Download (127.4 KB) - added by dcn@… 2 years ago.
output from sudo port -v install xorg-server
bigglestest1.py.zip Download (0.7 KB) - added by dcn@… 2 years ago.

Change History

  Changed 2 years ago by jeremyhu@…

  • status changed from new to assigned
  • description modified (diff)
  • milestone set to 2.5.0

That crash you mentioned is completely unrelated.

Can you try with the latest version? I haven't been releasing betas for Leopard, so you'll need to build it yourself on MacPorts (sudo port -v install xorg-server). Then just launch /Applications/MacPorts/X11.app

  Changed 2 years ago by dcn@…

I checked again and the direct biggles install actually crashes Python 2.5, so just take the Macports install as the origin of the problem. Macports installs its own x11 code when installing other applications, but biggles calls both that code and the Xquartz x11 saerver via /usr/bin

I'll try the macports xorg-server install as you suggest and report back.

  Changed 2 years ago by dcn@…

A question: port info xorg-server gives the result: xorg-server @1.7.2 (x11, devel) which doesn't sound like it's version 2.5.0

Am I misunderstanding things or is there a way to access the latest version?

Incidentally, I don't currently show xorg-sever installed under macports (port installed name:x), might that explain the whole problem?

  Changed 2 years ago by dcn@…

sudo port -v install xorg-server

Install broke.

Final lines of installation:

LINK X11.bin

Undefined symbols:

"_xp_set_dock_proxy", referenced from:

_xprAppleWMProcs in libXquartzXpr.a(xprAppleWM.o)

ld: symbol(s) not found collect2: ld returned 1 exit status make[4]: *** [X11.bin] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1

Warning: the following items did not execute (for xorg-server): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing.

Changed 2 years ago by dcn@…

output from sudo port -v install xorg-server

  Changed 2 years ago by jeremyhu@…

Your Xplugin.h is newer than your libXplugin because you used the combo update over 2.4.0.

Install XQuartz 2.4.0 to get the newer libXplugin, then install xorg-server from MacPorts.

2.4.0 and 2.5.0 are package versions. The server versions are the 1.x versions.

  Changed 2 years ago by dcn@…

Yes, I had to reninstall the 10.5.8 combo install over top of XQuartz 2.4.0, because the XQuartz 2.4.0 server broke the py26-biggles Macports install.

I'll try as you suggest.

  Changed 2 years ago by dcn@…

OK, after I reinstalled XQuartz 2.4.0, xorg-server installed properly using Macports, but py26-biggles is broken again for the test programs on the Biggles sourceforge site:

$ python bigglestest1.py Error: Unresolved inheritance operation

My suspicion is that biggles is using the XQuartz x11 server, which is what I think caused the problem last time, and necessitated reinstalling the OSX 10.5.8 combo update.

See thread at  http://www.mail-archive.com/macports-users@lists.macosforge.org/msg17579.html

A possible solution might be to get py26-biggles to use the Macports-installed xorg-server, but how do I do that?

  Changed 2 years ago by jeremyhu@…

biggles will use whichever X11 server you are running. Are you running /Applications/Utilities/X11.app or /Applications/MacPorts/X11.app ? The former is from xquartz.macosforge.org.

  Changed 2 years ago by dcn@…

I have both installed. If I run the Macports version (2.5.0) before running Python and biggles, the XQuartz version (2.4.0) opens and is the server used by biggles. How do I either set 2.5.0 as the default, remove 2.4.0, or get Python to run biggles using 2.5.0?

follow-up: ↓ 12   Changed 2 years ago by jeremyhu@…

The 2.4.0 version is starting because your DISPLAY variable is pointing to the launchd socket that is for the 2.4.0 version (that is default). You need to start an xterm from MacPorts X11 and run it from there if you want to run it in that server or change your configuration so launchd uses the MacPorts X11 server.

  Changed 2 years ago by jeremyhu@…

I have installed py26-biggles. Please attach your bigglestest1.py

in reply to: ↑ 10 ; follow-up: ↓ 13   Changed 2 years ago by dcn@…

Replying to jeremyhu@…:

The 2.4.0 version is starting because your DISPLAY variable is pointing to the launchd socket that is for the 2.4.0 version (that is default). You need to start an xterm from MacPorts X11 and run it from there if you want to run it in that server or change your configuration so launchd uses the MacPorts X11 server.

Sorry to be dumb, but how do I change my config to get launchd to use tge Macports x11 server?

Changed 2 years ago by dcn@…

in reply to: ↑ 12   Changed 2 years ago by dcn@…

Replying to dcn@…:

Replying to jeremyhu@…:

The 2.4.0 version is starting because your DISPLAY variable is pointing to the launchd socket that is for the 2.4.0 version (that is default). You need to start an xterm from MacPorts X11 and run it from there if you want to run it in that server or change your configuration so launchd uses the MacPorts X11 server.

Sorry to be dumb, but how do I change my config to get launchd to use tge Macports x11 server?

OK, I did run the Macports x11, opened an xterm, and tried to run the bigglestest program, same error message.

  Changed 2 years ago by dcn@…

FWIW, the line in the bigglestest program that triggers the error invokes the biggles command plot.show()

Running otool on plot shows three /usr/lib files on which plot depends:

$ otool -L /opt/local/bin/plot /opt/local/bin/plot:

/opt/local/lib/libplot.2.dylib (compatibility version 5.0.0, current version 5.4.0) /opt/local/lib/libXaw.7.dylib (compatibility version 8.0.0, current version 8.0.0) /opt/local/lib/libXmu.6.dylib (compatibility version 9.0.0, current version 9.0.0) /opt/local/lib/libXt.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libSM.6.dylib (compatibility version 7.0.0, current version 7.1.0) /opt/local/lib/libICE.6.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) /opt/local/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/lib/libXau.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libXdmcp.6.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libpng12.0.dylib (compatibility version 42.0.0, current version 42.0.0) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 292.4.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4)

  Changed 2 years ago by dcn@…

This might be relevant: ticket #19576:

 http://trac.macports.org/ticket/19576

Same error for 'nedit', required a recompile. This one probably requires a recompile of plotutils (at a guess).

  Changed 2 years ago by jeremyhu@…

  • status changed from assigned to closed

Your test code works fine for me with the latest betas of 2.5.0.

Note: See TracTickets for help on using tickets.