Bug ID |
11438
|
Summary |
Can't apply a filter using the "!=" operator in the Qt interface
|
Product |
Wireshark
|
Version |
Git
|
Hardware |
All
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Qt UI
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Wireshark 1.99.9 (v1.99.9rc0-175-g9d0cb0e from master)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 4.8.6, with libpcap, without POSIX capabilities,
without libnl, with libz 1.2.8, with GLib 2.42.2, without SMI, with c-ares
1.10.0, with Lua 5.2, with GnuTLS 3.3.16, with Gcrypt 1.6.3, without Kerberos,
without GeoIP, without PortAudio, without AirPcap.
Running on Linux 4.0.8-200.fc21.x86_64, with locale C, with libpcap version
1.7.3, with libz 1.2.8, with GnuTLS 3.3.16, with Gcrypt 1.6.3.
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (with SSE4.2)
Built using gcc 4.9.2 20150212 (Red Hat 4.9.2-6).
--
I regularly use the != operator for filtering--even though it "may have
unexpected results" (and the filter bar ends up yellow to warn me about this).
The Qt UI, however, doesn't let me use the filter at all. I can type in, for
example:
diameter.cmd.code != 280
but pressing Enter or even clicking the --> ("apply this filter") button
doesn't apply the filter. The only indications that something is wrong is the
yellow background and the (somewhat transient) warning in the lower left about
the possibly unexpected results.
[Yes, the above filter is just shorthand for "diameter && !(diameter.cmd.code
== 280)". I'm lazy that way ;-).]
You are receiving this mail because:
- You are watching all bug changes.