This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

MAC OSX 10.6.3 - When I Open Wireshark it shows on dock then closes

1

When I open Wireshark, it just shows on the dock as if it opened, then it closes itself, why is this?

When I run it using terminal it says: The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) does not exist dyld: Library not loaded: /usr/X11/lib/libfreetype.6.dylib Referenced from: /Applications/Wireshark.app/Contents/Resources/bin/wireshark-bin Reason: Incompatible library version: wireshark-bin requires version 13.0.0 or later, but libfreetype.6.dylib provides version 10.0.0

What does this mean?

asked 01 May '11, 23:32

Tim%20Nethers's gravatar image

Tim Nethers
16●2●2●4
accept rate: 0%

retagged 14 Jun '11, 19:01

helloworld's gravatar image

helloworld
3.1k●4●20●41

One Answer:

1

Apparently, the libfreetype you're using is incompatible with Wireshark. Others have had similar problems (here and here), and it seems to be related to a foul DYLD_LIBRARY_PATH. The second link (referring to gnuplot but same problem here) provides a temporary(?) workaround:

  1. Open the folder /Applications in the finder
  2. Right-click on Wireshark.app and select "Show package contents"
  3. Navigate to /Applications/Wireshark.app/Contents/Resources/bin
  4. Right-click on the file "wireshark" and select "Open with -> Other ... -> TextEdit.app"
  5. Change the line:

from: DYLD_LIBRARY_PATH="${ROOT}/lib:${DYLD_LIBRARY_PATH}"
to: DYLD_LIBRARY_PATH="${ROOT}/lib"

and

from: DYLD_FRAMEWORK_PATH
to: DYLD_FRAMEWORK_PATH="${ROOT}/lib"

EDIT: If the workaround above doesn't work for you, try re-installing freetype [from MacPorts].

answered 02 May '11, 07:01

bstn's gravatar image

bstn
375●1●4●15
accept rate: 14%

edited 02 May '11, 12:14

The first one already existed with $TOP in place of ${ROOT} The second did not exist.

(02 May '11, 09:25) Tim Nethers

Someone else had a similar problem with libfreetype recently and resolved it by performing a system update.

(14 Jun '11, 19:00) helloworld