[opensuse] Wireshark busted
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/11/2016 02:42 PM, 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.
Forgot to mention, this is on openSUSE 13.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2016-09-11 a las 14:48 -0400, James Knott escribió:
Looks like someone goofed with the update.
Forgot to mention, this is on openSUSE 13.1
Runs here, but I have not updated recently. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlfVp7kACgkQja8UbcUWM1yQiQEAity4EJBZJrLE/wcU3hZVjWIZ fPTofMGAxrNEYGB/gUMA/isYzwbwWutxTCd4MnOzpCvTwsTgdTruj5SakLjq3vAu =mKrF -----END PGP SIGNATURE-----
On 09/11/2016 02:48 PM, James Knott wrote:
On 09/11/2016 02:42 PM, 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.
Forgot to mention, this is on openSUSE 13.1
I installed an older version and got it going again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Sep 12, 2016 at 09:08:40AM +0930, Rodney Baker 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, packet capture permissions do not impact whether the binary will execute. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 09/12/2016 01:50 AM, Marcus Meissner wrote:
What does
rpm -V wireshark
show? Some permissions problems might have broken it
It doesn't show anything. There's no output from that command. Regardless, I installed an older version, which works. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/11/2016 02:42 PM, 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.
Further on this: I found that /usr/bin/wireshark is an old version and installing the latest package does not replace it. I then renamed it and tried installing again, but the new version still did not appear. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/11/2016 02:42 PM, 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.
Further on this: I found that /usr/bin/wireshark is an old version and installing the latest package does not replace it. I then renamed it and tried installing again, but the new version still did not appear. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/14/2016 12:13 PM, James Knott wrote:
On 09/11/2016 02:42 PM, 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.
Further on this:
I found that /usr/bin/wireshark is an old version and installing the latest package does not replace it. I then renamed it and tried installing again, but the new version still did not appear.
which wireshark should show if it is located in more then one location. And your $PATH will determine which ones runs. -- Ken linux since 1994 S.u.S.E./openSUSE since 1996 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/14/2016 12:39 PM, Ken Schneider wrote:
which wireshark
should show if it is located in more then one location. And your $PATH will determine which ones runs.
"Which wireshark" is what revealed the problem, when I tried it on another computer. When it couldn't find it, I checked the menu to see what it was using. That's where I first saw wireshark-gtk. The old wireshark had a write date of Aug 1, so it changed since then. It happened between version 2.0.5-195.1, which was the one that worked and 2.2.0-204.1, which didn't. "Which Wireshark" doesn't find wireshark-gtk, only wireshark. However, between adding that symlink and clearing that old version out of the menu cache, the problem is now gone. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/11/2016 02:42 PM, 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.
Found the problem. It appears the command for starting Wireshark changed from "wireshark" to "wireshark-gtk". I had long used just wireshark and the cached "Wireshark" in my start menu also tried to start the old "wireshare", but the menu item System>Monitor>Wireshark was correct. I use Wireshark so often I normally use the cached one at the top of the start menu, instead of having to dig down through the menu. I'll also add a symlink from wireshark-gtk to wireshark so that I don't see this problem at the command line either. Moral of the story, if the cached version at the top of the menu doesn't work, try going directly to the original menu item. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carlos E. R. -
Dutch Ingraham -
James Knott -
Ken Schneider -
Marcus Meissner -
Rodney Baker