[SOLVED] WIreshark 2.0 segfaults on Slackware64-current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using 14.1, and no I have not made any progress in getting a build to work with Qt, nor am I getting any useful traceback information that would help someone figure it out. The gdb traceback seems to imply something is seriously wrong, like the stack got overwritten.
Those distros split the application up into multiple packages. Perhaps you didn't download the one that has the binary? There is a core wireshark-2.0.0 package, but also wireshark-ui-gtk and wireshark-ui-qt (which contain the UI binaries).
I stand corrected. I didn't know that was the case with other distros; that could be because Slackware doesn't bother with such nonsense, and puts it all into one package. Oh well. I'm going to keep on running 1.12.8 until I see that 2.0.0 has been fixed.
Someone just opened a Wireshark bug report for the same problem: https://bugs.wireshark.org/bugzilla/...g.cgi?id=11833
I can't be sure, but it does NOT looks like he is running Slackware, so this is probably not a Slackware-specific problem.
And... the bug is now marked Fixed, Resolved. That was really fast. I tried the patch which is linked from the bug report, and it does result in a working Wireshark-2.0 with Qt UI on Slackware. (I'm not suggesting anyone needs to try it, but it tells me that this will be fixed in the next Wireshark release, and also that it wasn't a problem specific to Slackware.)
And... the bug is now marked Fixed, Resolved. That was really fast. I tried the patch which is linked from the bug report, and it does result in a working Wireshark-2.0 with Qt UI on Slackware. (I'm not suggesting anyone needs to try it, but it tells me that this will be fixed in the next Wireshark release, and also that it wasn't a problem specific to Slackware.)
Thanks for posting about the fix. I was able to apply the patch to the source, and re-compile, and it successfully compiled and ran without a segfault. Wonderful!
NOTE: To those who find it rather daunting to find the patch from the bug report (it is indeed linked, but rather difficult to find), so for convenience's sake, I will post it here. Another testimony to the power of open source!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.