Faisal Moledina wrote:
On Tue, Dec 29, 2009 at 5:32 PM, David Nicholls <[email protected]> wrote:
Thanks,
Perhaps the problem is XQuartz 2.4.0
snip
I might reinstall the Leopard 10.5.8 combo update again to overwrite the
XQuartz 2.4.0 files and see what happens.
That actually brings up a question I have for the MacPorts community.
Do ports that depend on X11 ports from MacPorts not open X windows
using the MacPorts-provided X server? That is, to show this plot, it
seems to open up in the System X11 (judging from the icon in the dock,
which is different from that of /Applications/MacPorts/X11.app). I
don't have XQuartz 2.4.0 installed in order to replicate this error,
but why should this cause an issue (if it is the issue) for David?
Faisal
I logged a bug report on the XQuartz site:
http://xquartz.macosforge.org/trac/ticket/337 which includes the
/Library/Logs crash report which appears to be relevant to the problem.
The system X11 install is implicated. But it would be nice if the
Macports x11 kept control of the process rather than letting it out to
the system x11.
DN
--
__________
ANU RSAA Mt Stromlo
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
