On Jan 28, 2008, at 00:13, William Davis wrote:
Begin forwarded message:
From: Jeremy Huddleston <jeremyhu@berkeley.edu> Date: January 27, 2008 6:06:35 PM EST To: Fred Dushin <fred@dushin.net> Cc: x11-users@lists.apple.com, Harald Hanche-Olsen <hanche@math.ntnu.no> Subject: Re: Trying to revert X11 after 2.1.3 install
On Jan 27, 2008, at 09:27, Fred Dushin wrote:
Starting wireshark is still killing my X server (after reverting back to 2.0, and then upgrading to 2.1.3). I'm attaching the report that would go to Apple (and I assume not prioritized?).
I built wireshark using a fresh install of macports 1.6.0, after doing an upgrade from 10.4.latest to 10.5, and then 10.5.1.
Here's what otool is telling me (interesting that it's taking libXrender from macports -- now that I think if it, I wonder if I built my macports when I only had X11User -- not X11SDK instaled):
macports will always do this... one of the reasons I'm considering dropping macports and looking into fink... <======== NOTE
Thread 1 Crashed: 0 X 0x000b0088 fbSolid + 600
This is already in the buglist in trac, and one of the bugs that I think/hope will be fixed automagically by out switch to 1.4 since I think most of this code was reworked by x.org during that transition (not 100% certain of that). We still have one major regression in 1.4 over 1.3 that Ben and I are trying to work out before we release a drop-in beta Xquartz binary for you guys to test out.
Please see the line marked NOTE above
It's disorienting to be thrown into a thread with no context or explanation like this. It sounds to me like Fred Dushin is noting that a wireshark installed using MacPorts is linking with its own xrender library instead of the system's, and Jeremy Huddleston points out that MacPorts will always do this, and that he's considering leaving MacPorts because of this. So what is the problem with linking with the MacPorts xrender? Is this a problem for all ports or just wireshark? Should we change to using the system's xrender instead, or is there a bug in the xrender port that we should be fixing? If Jeremy or Fred would like to come to this list to discuss the matter I'm sure we could begin a dialog of some sort.