I previously had Wireshark 1.4.6 Intel 64 installed on Mac OS X 10.6. I installed Wireshark 1.8.1 Intel 64 over it by executing the installer package. The installation claimed to be successful. When I tried to launch it, I got the error message Couldn't load module /Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/interlink.so: dlopen(/Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/interlink.so, 10): Symbol not found: _dissector_get_port_handle Referenced from: /Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/interlink.so Expected in: flat namespace in /Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/interlink.so I clicked the OK button to acknowledge that message and I got another error message Couldn't load module /Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/sercosiii.so: dlopen(/Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/sercosiii.so, 10): Symbol not found: _dissector_add Referenced from: /Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/sercosiii.so Expected in: flat namespace in /Applications/Wireshark.app/Contents/Resources/lib/wireshark/plugins/sercosiii.so I clicked the OK button to acknowledge that message and Wireshark quit. Any suggestions? asked 01 Aug '12, 19:22 Rosenberg |
One Answer:
Sounds like bug 7401. Removing Wireshark removed the stale plugin (it's a built-in dissector in 1.8.x, so, instead of replacing the plugin with an updated version, the installer just left the un-updated version behind). answered 01 Aug '12, 23:17 Guy Harris ♦♦ edited 01 Aug '12, 23:20 |
When I did the installation, I was running under an unprivileged account, and when prompted during the installation process, I entered the password for the Administrator account. As reported above, the installation reported it was successful, but Wireshark won't run. I then removed Wireshark, logged in as the Administrator and re-installed Wireshark. Whatever the problem was, this seems to have fixed it. Wireshark no longer quits when run under either the Administrator account or the unprivileged account.