I'm preparing WS OS X install hints for an international Cisco teachers conf next week. In the past, the WS OSX installer has had a utilities folder with a script / readme for setting up a first time install. I notice the current installer has a single file - no utilities folder. Also, in the past the readme has not been accurate, and the startup script did not work, so I've handheld my students through first time WS installs. There were several BASH commands that had to be run. So - my questions - 1 I presume x11 still must be installed /before/ wireshark is installed 2 Does the current installer properly put everything in running order with perms on the right folders, or is there still that dance to do on first installs, creating foldes and setting permissions? Thanks very much in advance - wish I had a Mac without WS to verify - Regards, John Gonder asked 21 Jun '11, 09:34  packetlevel |
2 Answers:
answered 23 Jun '11, 10:45  Guy Harris ♦♦ |
A comment, perhaps not an answer. I experienced the same "...It would appear in the dock for a second then disappear" issue on a MacBook Pro running 10.6.7 (and now 10.6.8) and discovered my problem: I have an older MBP and it's a Core Duo 32bit CPU. The Wireshark 1.6.0 download labeled as OS X 10.6 (Snow Leopard) Intel 64-bit .dmg did not work, despite reading all help articles here. What did work immediately is the download labeled OS X 10.5 (Leopard) Intel 32-bit .dmg. Having used Wireshark successfully, including the various install issues with permissions etc. prior to a clean re-install/full update cycle I was a bit baffled. Perhaps the download that works on the Core Duo CPUs without any issues could be amended to note that it works with Snow leopard, on 32 bit CPUs (like my early 2006 MBP, and a similar mini)... jb answered 24 Jun '11, 15:07  exmixer |
Thanks for chiming in - after posting the other day I did some testing. I did an install of 1.6 on a new macmini. X11, being part of the default install these days is not a problem anymore, yes. The current installer 1) puts the app in 2) creates the Library/local/bin folder, although with /aliases/ to the command line binaries, not they themselves. WS did not run, even after a reboot. It would appear in the dock for a second then disappear, even if x11 was already running (which was once a problem - WS could not load x11 by itself - hence my checking for this). This unit was 10.6.4 out of the box - so, I updated it to 10.6.7, all updates, cold booted, removed then re-installed WS1.6, checked perms on Library/local/bin, cold booted and WS ran and saw all NICs. The last installer that ran first time with no need for CLI help was 1.4.0 (I put it on our new iMacs previously). Hope this helps in seeing what variable there might be in this process. My problem is I run out of new machines to test install variations on. Once WS has run, subsequent updates work. It's just at the start of semesters as new groups of students put it in for the first time that I see the current gotchas. It makes it hard for me to be scientific about troubleshooting - we just shotgun it til it works; e.g. install 1.4.0, then update. Sorry I don't have anything more precise to offer in terms of data. If you have a specific test that might be helpful, I could do that on one of the remaining new Macs in July. Regards, John Gonder
(The only things that should be posted as answers are answers to the original question; this is a Q&A site, not a forum. I converted your reply to a comment.)
The problem you're seeing is a separate problem, due to a number of issues; if all of the support libraries used by Wireshark, including GTK+, were built against the SDK rather than the libraries on the build system, that wouldn't happen. The update to 10.6.7 probably would have sufficed, as it would have updated libfreetype to the same version as the one on the Wireshark Snow Leopard buildbot.