I get While WS is open, its windows can be displayed or hidden by displaying or hiding the X11 app. The first time this version of WS is run it may take several mins before the main window is displayed while font caches are built. I get that message. but it never starts up. MBP OS X snow lep. 10.6 asked 11 Feb '11, 16:52  avant_guard3 edited 29 Feb '12, 19:04  cmaynard ♦♦ |
2 Answers:
Ditto. Running it from the command line bash-3.2# /Applications/Wireshark.app/Contents/MacOS/Wireshark 2011-02-13 02:42:32.400 defaults[77170:903] The domain/default pair of (kCFPreferencesAnyApplication, AppleAquaColorVariant) does not exist 2011-02-13 02:42:32.420 defaults[77171:903] The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) does not exist dyld: Library not loaded: /usr/X11/lib/libpng12.0.dylib Referenced from: /Applications/Wireshark.app/Contents/Resources/bin/wireshark-bin Reason: Incompatible library version: wireshark-bin requires version 45.0.0 or later, but libpng12.0.dylib provides version 42.0.0 bash-3.2# I've got current Xcode and X11 XQuartz 2.3.5 installed on my machine. port upgrade libpng on macports is at 1.2.40. wireshark seems to be looking for a libpng with an entirely different numbering convention. Whuzzup? answered 13 Feb '11, 01:48  SGBotsford |
Open the ChmodBPF script, which is located in /Library/StartupItems/ChmodBPF/ChmodBPF, in a text editor. Add a chown line so that the file looks like this: ... chgrp admin /dev/bpf chmod g+rw /dev/bpf chown foobar:admin /dev/bpf* } ... But replace foobar here with the user you want to run Wireshark under. Save the file. answered 02 Jan '12, 10:13  Michael Lucas |
Ok. I've got a working wireshark. Did the macport version.
Comment to the developers: If you want portable code, do not write to the lastest version of the library unless you need a feature from that newer version.
If "the developers" means the Wireshark developers, we don't write to libpng at all, we write to GTK+ (and not the latest version); GTK+ builds with libpng. The problem is the version with which GTK+ is built; the build procedure for GTK+ is oriented towards building with the version installed on the machine, not with the version in, for OS X, an SDK.