Like Myron, I finally built xorg-server (along with wireshark) from
scratch using gcc-4.2 instead of gcc-4.0 by totally dumping /opt with
"sudo rm -rf /opt" and reinstalling from .dmg. Now, wireshark 1.8 now
works without X11 kicking its legs out from under it (i.e., X11 used to
crash, taking wireshark along with it). But starting up wireshark
requires a very klunky workflow:
I now have to start Terminal, then do a "sudo xinit" and then when an
xterm window starts up in the top left of my screen, enter "wireshark"
to start up wireshark. So, it appears that my original problem with
wireshark and X11 was because I was using the X11 that Apple provided
and it somehow clashed with the new version 1.8 of wireshark.
I used to have a nice Finder-based app shell named "Wireshark.app" which
allowed me to hide a script within it that basically issued this command:
/usr/bin/open -a /Applications/Utilities/X11.app /opt/local/bin/wireshark
And double-clicking on Wireshark.app in Finder would start wireshark
within the X11 located in /Applications/Utilities. I can't seem to swap
it out with this:
/usr/bin/open -a /Applications/MacPorts/X11.app /opt/local/bin/wireshark
Any pointers?
On 7/18/12 09:51, myron wrote:
I installed the xorg-server and now wireshark works fine. Thanks for
your help.
--myron
=================================
Myron Kowalski
MoCoSIN Network/Systems Administrator
Moravian College
my...@moravian.edu <mailto:my...@moravian.edu>
(610) 861-1441
On Jul 17, 2012, at 1:46 PM, Jeremy Huddleston Sequoia wrote:
Ok, now that someone has provided a crash report...
This smells like https://trac.macports.org/ticket/30927 to me.
Update your version of XQuartz, or use the xorg-server port.
--Jeremy
On Jul 17, 2012, at 8:03 AM, Brandon Allbery <allber...@gmail.com
<mailto:allber...@gmail.com>> wrote:
On Tue, Jul 17, 2012 at 9:20 AM, myron <kowal...@cs.moravian.edu
<mailto:kowal...@cs.moravian.edu>> wrote:
I had been following a thread about wireshark the other day and
decided to
start up my wireshark which I had
just upgraded. I hadn't used it for a few months, and it was
working then.
Now I'm getting a similar problem as the
other poster. I didn't get what his solution was.
I start in an X11 window. An empty gray box appears and then everything
crashes. Here's what in problem report that
comes up.
For what it's worth, I am still not seeing this --- but I'm using
XQuartz,
not stock (Lion) X11.app. I *did* see one oddity, though: it didn't
display its splash screen or open its main window until I explicitly
switched focus to XQuartz. It seemed to be "hung" before I did that.
--
brandon s allbery allber...@gmail.com <mailto:allber...@gmail.com>
wandering unix systems administrator (available) (412) 475-9364
vm/sms
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
<mailto:macports-users@lists.macosforge.org>
http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users