| Bug ID |
11058
|
| Summary |
annoying popup when trying to capture on bonds
|
| Product |
Wireshark
|
| Version |
1.10.12
|
| Hardware |
x86
|
| OS |
Fedora
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13515 [details]
screenshot of the issue
Build Information:
wireshark 1.10.12 (Git Rev Unknown from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (32-bit) with GTK+ 2.24.24, with Cairo 1.13.1, with Pango 1.36.1, with
GLib 2.38.2, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without
Python,
with GnuTLS 3.1.28, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Aug 4 2013 06:58:01), with AirPcap.
Running on Linux 3.15.8-200.fc20.i686+PAE, with locale en_US.UTF-8, with
libpcap
version 1.5.3, with libz 1.2.8, GnuTLS 3.1.25, Gcrypt 1.5.3, without AirPcap.
Built using gcc 4.8.3 20140911 (Red Hat 4.8.3-7).
--
Hi,
when a bond interface is selected for capture in the "capture option" windows,
and as soon a character is typed in the capture filter field, a popup persist
being displayed with "The link type of interface <name> was not specified."
problem seems linked with what is described in
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7135 except that i have
never seen it fixed.
a workaround to be able to type a complete capture filter is to type it in the
"edit interface setting windows", however it is not preventing the popup to be
displayed once exited of this window.
issue seems linked to the fact that the bond interfaces are the only ones for
which there is no default link layer type pre-filled in the preference /
interface options, and none is selectable in the drop down list.
we end up always launching wireshark with all filter options via the cli
instead of setting it up via the GUI.
surprisingly, the issue disappears when using wireshark compiled from sources
(./configure -with-qt=no -with-gtk2=yes --with-gtk3=no --with-adns
--enable-setuid-install --with-c-ares )
Thanks for support
You are receiving this mail because:
- You are watching all bug changes.