LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-25-2015, 10:32 AM   #1
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current,Ubuntu,openSuSE,Manjaro
Posts: 816
Blog Entries: 9

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
WIreshark 2.0 segfaults on Slackware64-current


Hey guys, I have a slight annoyance which I would like to know how to fix. Not a big one, but one that bugs me nonetheless.

Wireshark released their 2.0 version not too long ago, and I'm having trouble getting it to run. Compiling is no problem; the one issue I had (outdated version of qt5) I fixed by upgrading to Alien BOB's latest. However, if I try to run the resulting package, I get a 'Segmentation fault'. However, if I compile the last version (1.12.8), it compiles and runs with no problem. Is there something in the configuration option of the SlackBuild that I would need to change to fix this, or is it something else? Any ideas would be greatly appreciated. Let me know if there's more information I need to provide.

Regards,

Matt
 
Old 11-26-2015, 09:02 AM   #2
JackHair
Member
 
Registered: Aug 2009
Location: Netherlands
Distribution: Slackware64-current
Posts: 167

Rep: Reputation: 39
I'm having the same issues with the QT client. It just segfaults. But the GTK+ client works fine. I didn't install QT5 btw, I just used to stock SlackBuild from SBo with only the version edited to 2.0.0.

Last edited by JackHair; 11-27-2015 at 01:50 AM. Reason: I should've added I'm running 2.0.0
 
Old 11-26-2015, 01:18 PM   #3
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current,Ubuntu,openSuSE,Manjaro
Posts: 816

Original Poster
Blog Entries: 9

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by JackHair View Post
I'm having the same issues with the QT client. It just segfaults. But the GTK+ client works fine. I didn't install QT5 btw, I just used to stock SlackBuild from SBo with only the version edited.
Yeah, I'm running the previous version, 1.12.8. Seems the sane thing to do, given the situation. Maybe the maintainer can figure out some magic incantation he can perform on the SlackBuild to keep the new 2.0.0 version from segfaulting. I sure can't figure it out. And it's not like the previous version was so bad that the 2.x version is a must-have.
 
Old 11-26-2015, 10:21 PM   #4
ljb643
Member
 
Registered: Nov 2003
Posts: 454

Rep: Reputation: Disabled
Same here. Slackware 14.1 (32-bit), compiled wireshark-2.0.0 from source. I'm using the Slackware-provided Qt-4.8.7. (Not using Slackbuilds.org scripts.) When built with the Qt UI, it segfaults on startup. The traceback looks like this:
Code:
#0  QList (l=..., this=0x864f940 <colors_>)
    at /usr/lib/qt/include/QtCore/qlist.h:122
No locals.
#1  __static_initialization_and_destruction_0 (__initialize_p=1,
    __priority=65535) at io_graph_dialog.cpp:82
No locals.
#2  _GLOBAL__sub_I_colors_ () at io_graph_dialog.cpp:2319
No locals.
#3  0x083a31fd in __do_global_ctors_aux ()
No symbol table info available.
#4  0x08073664 in _init ()
No symbol table info available.
#5  0x00000000 in ?? ()
No symbol table info available.
All I can get from that is that it crashes when Wireshark's ui/qt/io_graph_dialog.cpp tries to initialize a Qt List of colors.

There was some discussion about the Wireshark decision to drop Gtk+ and go with only Qt, and this is not a good sign.
 
Old 11-26-2015, 11:20 PM   #5
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current,Ubuntu,openSuSE,Manjaro
Posts: 816

Original Poster
Blog Entries: 9

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by ljb643 View Post
Same here. Slackware 14.1 (32-bit), compiled wireshark-2.0.0 from source. I'm using the Slackware-provided Qt-4.8.7. (Not using Slackbuilds.org scripts.) When built with the Qt UI, it segfaults on startup. The traceback looks like this:
Code:
#0  QList (l=..., this=0x864f940 <colors_>)
    at /usr/lib/qt/include/QtCore/qlist.h:122
No locals.
#1  __static_initialization_and_destruction_0 (__initialize_p=1,
    __priority=65535) at io_graph_dialog.cpp:82
No locals.
#2  _GLOBAL__sub_I_colors_ () at io_graph_dialog.cpp:2319
No locals.
#3  0x083a31fd in __do_global_ctors_aux ()
No symbol table info available.
#4  0x08073664 in _init ()
No symbol table info available.
#5  0x00000000 in ?? ()
No symbol table info available.
All I can get from that is that it crashes when Wireshark's ui/qt/io_graph_dialog.cpp tries to initialize a Qt List of colors.

There was some discussion about the Wireshark decision to drop Gtk+ and go with only Qt, and this is not a good sign.
Indeed. Unless there is something that needs to be changed about the way Wireshark is compiled, I fear that no one will be able to run the 2.0 version. We'll see if someone else can figure it out, because I changed all the options in the SlackBuild that I thought was relevant, to no avail.
 
Old 11-27-2015, 06:35 AM   #6
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,698

Rep: Reputation: Disabled
Quote:
Originally Posted by JackHair View Post
I'm having the same issues with the QT client. It just segfaults. But the GTK+ client works fine. I didn't install QT5 btw, I just used to stock SlackBuild from SBo with only the version edited to 2.0.0.
I can confirm that version-bumping the script on SBo to 2.0.0 and building it with the stock qt-4.x or against qt5 /usr/bin/wireshark segfaults.
but as JackHair says, wireshark-gtk (using, by default, gtk+3) works fine so, if running the qt client is not mandatory, you can use that (in the meantime it gets fixed).
 
Old 11-27-2015, 09:06 AM   #7
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current,Ubuntu,openSuSE,Manjaro
Posts: 816

Original Poster
Blog Entries: 9

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by ponce View Post
I can confirm that version-bumping the script on SBo to 2.0.0 and building it with the stock qt-4.x or against qt5 /usr/bin/wireshark segfaults.
but as JackHair says, wireshark-gtk (using, by default, gtk+3) works fine so, if running the qt client is not mandatory, you can use that (in the meantime it gets fixed).
As I said before, it's not like 2.0.0 is mandatory. I can settle for staying at the older version, especially if it doesn't segfault. Much better, I think
 
Old 11-27-2015, 08:01 PM   #8
ljb643
Member
 
Registered: Nov 2003
Posts: 454

Rep: Reputation: Disabled
Quote:
Originally Posted by mattallmill View Post
As I said before, it's not like 2.0.0 is mandatory. I can settle for staying at the older version, especially if it doesn't segfault. Much better, I think
Just to clarify: Has anyone run the Qt version of Wireshark-1.12.x on Slackware? We know the Gtk+ version of 1.12.x works on Slackware, as does the Gtk+ version of 2.0.0. We know the Qt version of 2.0.0 crashes. So is this a Qt problem, or a "Qt with 2.0.0" problem?

I looked at the Wireshark mailing list and bugzilla, and was not able to find anything applicable. Perhaps 2.0.0 is too new, but I doubt it. It could be Slackware-specific, like some library version we are using is responsible. If the developers don't know about it, it probably won't get fixed. Anyone volunteer to either post to the list or open a bug report?
 
Old 11-27-2015, 08:43 PM   #9
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 481Reputation: 481Reputation: 481Reputation: 481Reputation: 481
This is not a put down in anyway to Ponce. He can use the help. But when you break 14.1 and then you decide for all of us that we need qt5 this tells me you need more help. Send your donations to slackbuilds. or do like I do maintain your own.
It is insane to think slackbuilds would take the pull request to allow so many qt5 dependencies. Yes I understand that many of the newer programs coming out are being developed with frame works widgets. The thing is slackware current is a qt4 build. and if people that run a github think they can just keep pushing qt5 down our throats before the operating system is built for it may need to go to ubuntu. and deal with the fact that no way should there be a dependencies for qjackctl or any other program that is making use use frame works to run qt4 programs. KDE does not do that. this is an example of merging pulls on a qt4 system an making the people of slackware 14.1 and current 14.2 break the stable stuff that is well known to work.

Right now for current they have pulled in changes that build one program and break many others oh that's current . No it is already in master and been pulled into 14.1 also.
If I was you I would pull slackbuilds git hub and checkout the the revision that is not broke.
As far as I am concerned slackbuilds is so broken and so big it would not be worth my time to fix.
easier to start your own.
Just the other day Pat said sorry Mozilla-fire fox no longer builds in 14.0 EOL end of the line. The fact is it is built on debian oldstable and what has changed is a glibc 2.13 like 14.0 and is a 4.7 gcc like 14.0 .It is cmake that has changed to handle new code.. It has nothing to do with right or wrong. it has to do with people thinking anyone can throw something on the git hub and oh it has to be right.
Pat could rebuild Cmake 3.0 like I did for 14.0. or you say that is slack 14.0 era.
then in that case if you love 14.0 you make your 14.0 work with new code.
But when it comes to slackbuilds it should be like end of line. fact is upgrading these programs in 14.1 after 2 years and pushing new dependencies is nuts. This is about current ok wtf curent is a qt4 system and is stable as can be. Why is Slack builds breaking current. it is as simple as making another branch. Branch transition I guess because current is an operating system that is stable in slackware. very rarely broken like wireshark.
Do not waist your time emailing the phoney emails of the maintainers or or sending them pull request or sending them patches they do not answer.
 
Old 11-27-2015, 09:12 PM   #10
ljb643
Member
 
Registered: Nov 2003
Posts: 454

Rep: Reputation: Disabled
To answer my own question, yes, the Qt version of wireshark-1.12.8 does work on Slackware-14.1. So the problem is specific to wireshark-2.0.0 with Qt.
 
Old 11-27-2015, 09:24 PM   #11
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 481Reputation: 481Reputation: 481Reputation: 481Reputation: 481
Quote:
Originally Posted by ljb643 View Post
To answer my own question, yes, the Qt version of wireshark-1.12.8 does work on Slackware-14.1. So the problem is specific to wireshark-2.0.0 with Qt.
you are absolutely right. you are using current and it is a qt4 system so your in the right direction. And if the latest program requires qt5 and you want to use the latest up to you slacker it is your slack. make it work. From what I read 2.0 require qt5 it uses widgets. if you want to build it you need to build qt5 from slack build. and the current in slackbuilds is 1.12 https://github.com/Ponce/slackbuilds...work/wireshark
 
Old 11-28-2015, 04:10 PM   #12
ljb643
Member
 
Registered: Nov 2003
Posts: 454

Rep: Reputation: Disabled
Quote:
Originally Posted by Drakeo View Post
you are absolutely right. you are using current and it is a qt4 system so your in the right direction. And if the latest program requires qt5 and you want to use the latest up to you slacker it is your slack. make it work. From what I read 2.0 require qt5 it uses widgets. if you want to build it you need to build qt5 from slack build. and the current in slackbuilds is 1.12 https://github.com/Ponce/slackbuilds...work/wireshark
(a) I'm not using Current, I'm using Slackware-14.1. (b) The configure script for wireshark-2.0.0 says the minimum version of QT is 4.7, as does the file doc/README.qt. Slackware-14.1 has 4.8.7 which meets this requirement. (c) The person who started this thread is getting the segfault with Qt5 also.

What is your source for "Wireshark 2.0.0 needs Qt5"?
 
Old 11-28-2015, 10:33 PM   #13
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 481Reputation: 481Reputation: 481Reputation: 481Reputation: 481
Quote:
What is your source for "Wireshark 2.0.0 needs Qt5"?
I stand corrected. Thank you have you got it built in current yet. ?
 
Old 11-29-2015, 02:42 PM   #14
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current,Ubuntu,openSuSE,Manjaro
Posts: 816

Original Poster
Blog Entries: 9

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Just on a lark, I went to pkgs.org, and downloaded another distro's package of wireshark-2.0.0 (OpenSUSE 13.2), and see whether it would work on Slackware. However, an interesting development occurred. After having converted it to Slackware-style and looking at the file contents via:
Code:
pico /var/log/packages/wireshark-2.0.0-x86_64-170.1
I looked at all the binaries in /usr/bin, and there was no wireshark binary!. The only interface available was tshark, which, after Googling the program, is the terminal-based version of wireshark. After this little experience, I'm wondering whether the Wireshark developer's much-vaunted move to Qt might not yet be ready for prime-time on any distro.
 
Old 11-29-2015, 04:14 PM   #15
ljb643
Member
 
Registered: Nov 2003
Posts: 454

Rep: Reputation: Disabled
Quote:
I stand corrected. Thank you have you got it built in current yet. ?
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.


Quote:
Just on a lark, I went to pkgs.org, and downloaded another distro's package of wireshark-2.0.0 (OpenSUSE 13.2), and see whether it would work on Slackware... I looked at all the binaries in /usr/bin, and there was no wireshark binary!.
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).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Skype segfaults in Slackware64 current multilib Gumboherpy Slackware 4 07-07-2015 06:21 PM
[SOLVED] wireshark-1.10.0 segfaults on Slackware64 tolip Linux - Newbie 15 07-07-2013 04:53 AM
google-chrome segfaults on Slackware64 -current TL_CLD Slackware 26 05-27-2012 11:13 AM
Slackware64 madplay segfaults disturbed1 Slackware 3 09-24-2009 06:46 AM
Slackware64-current: Creation of LUKS encrypted partition segfaults titopoquito Slackware 16 08-16-2009 05:02 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:53 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration