On Sun, Sep 11, 2016 at 09:03:39PM -0400, James Knott wrote:
On 09/11/2016 07:56 PM, Dutch Ingraham wrote:
On Sunday, 11 September 2016 2:42:52 PM ACST James Knott wrote:
There was a recent Wireshark update and now it doesn't work. If I try to start it from the command line, I get the error message "wireshark: error while loading shared libraries: libwiretap.so.5: cannot open shared object file: No such file or directory". However, the Wireshark file list shows /usr/lib64/libwiretap.so.6, which is linked to libwiretap.so.6.0.0. I then created a libwiretap.so.5 link to libwiretap.so.6.0.0 and it now chokes on libwireshark.so.6, but libwireshark.so.8 is there.
Looks like someone goofed with the update. This could be a permissions problem. Check the wireshark documentation or google "wireshark setcap". Packet capture requires root permissions but, rather than run wireshark with elevated privileges, setcap is used to set the capabilities to allow it to be run as a normal user.
This may or may not be related to your problem. YMMV. It's not related. Although the OP was woefully deficient in relevant details,
On Mon, Sep 12, 2016 at 09:08:40AM +0930, Rodney Baker wrote: packet capture permissions do not impact whether the binary will execute.
As I said, it was looking for one version of a file, not the one installed, for example libwiretap.so.6 vs libwiretap.so.5. Going back to an earlier Wireshark version got it going again.
What does rpm -V wireshark show? Some permissions problems might have broken it CIao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org