Wireshark-bugs: [Wireshark-bugs] [Bug 10640] wireshark 1.12.1 crashes on startup on Mac OS X 10.
Comment # 17
on bug 10640
from Guy Harris
(In reply to Andreas Fink from comment #15)
> The symlink is NOT the bug.
Correct. The *removal* of the symlink - placed there by the XQuartz installer,
XQuartz being an Apple project - by the Yosemite installer is the bug.
> I did a fresh install of OSX 10.10 in a VM and there is a directory in
> /usr/X11 not a symlink (might come from the command line developer tools).
No, it's part of the Yosemite installation (it appeared on a fresh installation
without the command-line developer tools), and it's probably done so that X11
binaries will run - they have to be able to run in order to fire up the fake
server, so that it can pop up the "you need to install X11" dialog.
The XQuartz installer removes the "enough of X11 to permit clients to start up"
/usr/X11, and replaces it with a symlink to /opt/X11.
> So you build against an old version of XQuarz and hence it wont work on
> 10.10 with XQuarz 2.7.7.
Nope, works fine. I:
installed 10.10.3 on a fresh VM;
installed Wireshark 1.12.5 on that VM;
launched Wireshark;
got the "you need to install X11" dialog, and installed the latest XQuartz;
re-launched Wireshark;
told the system where X11 was;
logged out and in again because that part of the process doesn't work very
smoothly (the right fix for *that* is to stop using an X11-based toolkit for
Wireshark);
shut down all X11 and Wireshark instances that popped up after logging in,
and launched Wireshark *again*;
and Wireshark popped up.
The problem is *not* "the packaged Wireshark won't work on anything after
Lion"; the problem is "whilst the packaged Wireshark will work on Snow Leopard
or later if there's proper X11 installation on the system - either the bundled
X11 up to Lion or XQuartz on Mountain Lion and later - upgrading to Yosemite
from an earlier release that has a proper XQuartz installation on the system
will break the XQuartz installation by removing the symbolic link from /usr/X11
to /opt/X11", and therefore the fix is to put the symbolic link back.
You are receiving this mail because:
- You are watching all bug changes.
