Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9866] New: Clearing filters does not seem to affect the packet list

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9866
Summary	Clearing filters does not seem to affect the packet list
Classification	Unclassified
Product	Wireshark
Version	1.11.x (Experimental)
Hardware	x86-64
OS	Mac OS X 10.9
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	Wireshark
Assignee	bugzilla-admin@wireshark.org
Reporter	edonahue@riverbed.com

Created attachment 12621 [details]
Video of the filter clearing failure

Build Information:
/Applications/Wireshark.app/Contents/MacOS/Wireshark -v
FIX: packet list heading menu sensitivity 
wireshark 1.11.2 (SVNRev 53411 from /trunk)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 (64-bit) with Qt 5.1.1 with GLib 2.36.0, with libpcap, with libz
1.2.3,
without POSIX capabilities, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, without Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT
Kerberos, with GeoIP, without PortAudio, with AirPcap.

Running on Mac OS X 10.9.2, build 13C64 (Darwin 13.1.0), with locale
en_US.UTF-8, with libpcap version 1.3.0 - Apple version 41, with libz 1.2.5,
GnuTLS 2.12.19, Gcrypt 1.5.0, without AirPcap.
       Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).

--
If I open a capture, filter it for something, then clear the filter, the packet
list remains filtered for what I was looking for.  Applying other filters don't
seem to have any affect either.  

Steps to reproduce:
1) Open a capture file
2) Filter for some combination of packets (in my video example, I used
dns.flags.rcode > 0)
3) Clear the filter with the X button

Behaviour Encountered:
The filter input field clears, but the packet list remains filtered based on
the filter you previously applied

Behaviour Expected:
The filter input field clears, and the packet list is returned to a
non-filtered state (all packets are shown)

Notes:
- Workaround by re-opening the capture
- In the attached video, I opened a capture, filtered using a pre-made button
and clicked X.  For some reason my mouse input was not captured in the video,
sorry.

---

      You are receiving this mail because:

• You are watching all bug changes.