This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Select enabled protocols issue on wireshark 1.12.6

0

Hello,

When I updated wireshark from 1.12.5 to 1.12.6, the entry Enabled protocols has suddenly disappeared from the menu Analyze.

Even if I press SHIFT+CTRL+E nothing happens.

My personal protocol name is correctly displayed in the capture window, but the dissector action is shown as Data field only.

In what condition the Analyze/Enabled protocols entry could disappear ?

Other items disappeared as well: Analyze/User Specified decodes Analyze/Expert info Analyze/Expert info Composite Analyze/Conversation Filter

My actual config:

Mageia5 Linux 64bits

wireshark 1.12.6 64bits

Thank you

BB

asked 19 Jul '15, 17:35

biba_paris's gravatar image

biba_paris
11114
accept rate: 0%


One Answer:

2

By any chance did you build /install the Qt GUI instead of the GTK based one?

Nothing changed in Wireshark 1.12.6 wrt those features, unless you launched the incomplete and buggy (in this branch) Qt GUI that did not have them.

answered 20 Jul '15, 11:41

Pascal%20Quantin's gravatar image

Pascal Quantin
5.5k1060
accept rate: 30%

Thank you for your fast reply.

Your answer reminded me that I have seen some qt packages update on Mageia5 these days.

But how to know if I'm using QT or Gtk gui ?

Here are some console messages when I launch wireshark:

QMetaObject::connectSlotsByName: No matching signal for on_bStart_clicked()
QMetaObject::connectSlotsByName: No matching signal for on_bStop_clicked()
FIX: packet list heading menu sensitivity
01:15:52.367  Dbg  FIX: timestamp types should be set elsewhere
01:15:52.367 Main Info fill_in_local_interfaces() starts
01:15:52.368 Capture Msg  Capture Interface List ...
01:15:52.368 Capture Dbg  sync_interface_list_open
01:15:52.368 Capture Dbg  sync_pipe_open_command
01:15:52.439 Capture Dbg  read 14 indicator: S empty value
01:15:52.439 Capture Dbg  sync_pipe_wait_for_child: wait till child closed
01:15:52.439 Capture Dbg  sync_pipe_wait_for_child: capture child closed after 0.000s
01:15:52.439 Capture Msg  Capture Interface Capabilities ...
01:15:52.439 Capture Dbg  sync_if_capabilities_open
01:15:52.439 Capture Dbg  sync_pipe_open_command
01:15:52.482 Capture Dbg  read 14 indicator: S empty value
01:15:52.482 Capture Dbg  sync_pipe_wait_for_child: wait till child closed
01:15:52.482 Capture Dbg  sync_pipe_wait_for_child: capture child closed after 0.000s
01:15:52.483 Capture Msg  Capture Interface Capabilities ...
01:15:52.483 Capture Dbg  sync_if_capabilities_open
01:15:52.483 Capture Dbg  sync_pipe_open_command
01:15:52.512 Capture Dbg  read 14 indicator: S empty value
01:15:52.512 Capture Dbg  sync_pipe_wait_for_child: wait till child closed
01:15:52.512 Capture Dbg  sync_pipe_wait_for_child: capture child closed after 0.000s
01:15:52.584 Capture Msg  Capture Interface Capabilities failed!
01:15:52.584 Capture Msg  Capture Interface Capabilities ...

etc...

(20 Jul '15, 16:34) biba_paris
1

That output means you're using the Qt-based GUI.

(20 Jul '15, 17:16) Hadriel

Thank you Hadriel, you are right.

In the description of the Mageia package, QT GUI is used.

If I understand, something happened to wireshark, after last lib64qt5core update.

I tried to reinstall qt5, but it has a huge number of Apps in its dependance tree.

I returned to my debian Jessie version (1.12.1) under GTK, until a solution is found for Mageia5 QT version.

(20 Jul '15, 23:35) biba_paris
1

Linux distro should not package a Wireshark 1.12.x version with Qt GUI: in this branch this graphical front-end is more a proof of concept than anything else and is not ready for production. It will be part of Wireshark 2.0.

(21 Jul '15, 03:51) Pascal Quantin

Thank you Pascal for your info.

Linux distros are time crunchers with their policies.

For example: As I told you, I launched wireshark 1.12.1 GTK under debian jessie.

Now, I'm facing a new problem:

The generic dissector plugin (http://wsgd.free.fr/) stopped working.

I had created a desc/wsgd files for a personnal protocol

The reason displayed is that glibc < 2.14 in debian jessie.

And no way to upgrade jessie (8.1)

Do I have to add a new os (like ubuntu) to overtake this issue ?

I'm wasting my time with os problems !!!

(21 Jul '15, 05:59) biba_paris

@biba_paris

If an answer has solved your issue, please accept the answer for the benefit of other users by clicking the checkmark icon next to the answer. Please read the FAQ for more information.

Your "answer" has been converted to a comment as that's how this site works. Please read the FAQ for more information.

(21 Jul '15, 06:11) grahamb ♦
showing 5 of 6 show 1 more comments