Wireshark-users: Re: [Wireshark-users] Wireshark-dev Digest, Vol 74, Issue 32
From: "Kumar, Chandan (Chandan)" <chandan.kumar@xxxxxxxxxxxxxxxxxx>
Date: Thu, 19 Jul 2012 11:40:44 +0530
 
Jakub/Wireshark-team
 
Dopa is nothing but rename of wireshark script means at the place of ./Wireshark we run as ./dopa . So I think there is no any problem with dopa. Can you give me any other debugging idea to resolve it. Right now I am using Wireshark-1.6.2 version.
 
Thanks in advanced.
 
Thanks
Chandan
~~~~~~~
============================================================================
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of wireshark-dev-request@xxxxxxxxxxxxx
Sent: Thursday, July 19, 2012 12:30 AM
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Wireshark-dev Digest, Vol 74, Issue 32
 
Send Wireshark-dev mailing list submissions to
        wireshark-dev@xxxxxxxxxxxxx
 
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
        wireshark-dev-request@xxxxxxxxxxxxx
 
You can reach the person managing the list at
        wireshark-dev-owner@xxxxxxxxxxxxx
 
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wireshark-dev digest..."
 
 
Today's Topics:
 
   1. tcap.tid display filter not applied as byte string
      (Arjan Van Der Oest)
   2. Wireshark-bug (Kumar, Chandan (Chandan))
   3. Re: Wireshark-bug (Jakub Zawadzki)
   4. Re: tcap.tid display filter not applied as byte   string
      (Christopher Maynard)
 
 
----------------------------------------------------------------------
 
Message: 1
Date: Wed, 18 Jul 2012 12:23:38 +0200
From: Arjan Van Der Oest <Arjan@xxxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: [Wireshark-dev] tcap.tid display filter not applied as byte
        string
Message-ID: <A749AFDD-0639-4FA0-A495-08425353BD87@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
 
Hi,
 
When using the TCAP dissector and clicking right on a TID value (i.e.: 0c0013c0) , selecting "Apply as Filter > Selected" the display filter will be composed as "tcap.tid == 0c0013c0" and WS will error on me with "tcap.tid == 0c0013c0" isn't a valid display filter: &quot;0c0013c0&quot; is not a valid byte string.
 
When manually changing the display filter to  "tcap.tid == 0c:00:13:c0 the problem is solved. It seems to me the 'Apply as filter...' command from the context menu is not behaving correctly.
 
Arjan
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
 
------------------------------
 
Message: 2
Date: Wed, 18 Jul 2012 17:37:50 +0530
From: "Kumar, Chandan (Chandan)" <chandan.kumar@xxxxxxxxxxxxxxxxxx>
To: "wireshark-dev@xxxxxxxxxxxxx" <wireshark-dev@xxxxxxxxxxxxx>
Subject: [Wireshark-dev] Wireshark-bug
Message-ID:
        <EDCB4994B292FB4192DFCA11D511ADB026EDAAED@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
       
Content-Type: text/plain; charset="us-ascii"
 
Hi All,
 
        Can anyone help me to resolve the following issue? When do I run Wireshark on Linux machine compilation goes fine but after opening the GUI with any pcap file, background I am getting these error messages? So what I have to do to remove these issue.
 
 
(dopa:20255): Gtk-CRITICAL **: gtk_menu_attach_to_widget: assertion `GTK_IS_MENU (menu)' failed
 
(dopa:4159): Gtk-CRITICAL **: gtk_tree_model_iter_n_children: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
 
(dopa:6369): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
 
(dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
 
(dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
 
 
Thanks
Chandan
~~~~~~~
 
-------------- next part --------------
An HTML attachment was scrubbed...
 
------------------------------
 
Message: 3
Date: Wed, 18 Jul 2012 15:31:16 +0200
From: Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Wireshark-bug
Message-ID: <20120718133115.GA12880@xxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
 
Hi,
 
On Wed, Jul 18, 2012 at 05:37:50PM +0530, Kumar, Chandan (Chandan) wrote:
> Can anyone help me to resolve the following issue?
> When do I run Wireshark on Linux machine compilation goes fine but after opening the GUI with any pcap file, background I am getting these error messages?
> So what I have to do to remove these issue.
>
> (dopa:20255): Gtk-CRITICAL **: gtk_menu_attach_to_widget: assertion `GTK_IS_MENU (menu)' failed
>
> (dopa:4159): Gtk-CRITICAL **: gtk_tree_model_iter_n_children: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
>
> (dopa:6369): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
>
> (dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
>
> (dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
 
Erm, these errors are from some 'dopa' program, not wireshark.
 
If you have any issues with *wireshark* please post output of wireshark --version
 
 
------------------------------
 
Message: 4
Date: Wed, 18 Jul 2012 14:28:55 +0000 (UTC)
From: Christopher Maynard <Christopher.Maynard@xxxxxxxxx>
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] tcap.tid display filter not applied as
        byte    string
Message-ID: <loom.20120718T162214-293@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=utf-8
 
Arjan Van Der Oest <Arjan@...> writes:
 
> When using the TCAP dissector and clicking right on a TID value (i.e.:
0c0013c0) , selecting "Apply as Filter > Selected" the display filter will be
composed as "tcap.tid == 0c0013c0" and WS will error on me with "tcap.tid ==
0c0013c0" isn't a valid display filter: &quot;0c0013c0&quot; is not a valid byte
string.
>
> When manually changing the display filter to ?"tcap.tid == 0c:00:13:c0 the
problem is solved. It seems to me the 'Apply as filter...' command from the
context menu is not behaving correctly.
 
Please file a bug report and include a small capture file for testing.
- Chris
 
 
 
 
------------------------------
 
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
 
 
End of Wireshark-dev Digest, Vol 74, Issue 32
*********************************************