Filter Expression dialog can only be opened once.
This issue was migrated from bug 6537 in our old bug tracker.
Original bug information:
Reporter: PaulK
Status: RESOLVED FIXED
Product: Wireshark
Component: GTK+ UI
OS: Windows XP
Platform: Other
Version: 1.6.3
Activity
Build Information: Version 1.6.3 (SVN Rev 39702 from /trunk-1.6)
Copyright 1998-2011 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 (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Nov 1 2011), with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 21022
Once the 'Filter Expression' dialog has been opened then closed, it cannot be opened again in the same instance of Wireshark. Steps to reproduce: 1. Open Wireshark. 2. Click on the 'Expression...' button. 3. Close the 'Filter Expression' dialog (by any means). 4. Click on the 'Expression...' button again. The 'Filter Expression' dialog does not re-open. I suspect that the modification for bug ID 6472 may have something to do with this: The file static variable 'window' remains non-NULL when the dialog is destroyed, so preventing a new dialog being created?added oswindows uigtk version1.6 labels
-
Yes, this bug was introduced when adding the patch for bug #6472 (closed). Unfortunately this was not well tested before propagated to version 1.4.10 and 1.6.3.
The proper fix would be to revert revision 39665, and bug #6472 (closed) has to be fixed using another solution.
-
(In reply to comment #1) > Yes, this bug was introduced when adding the patch for bug 6472. Unfortunately > this was not well tested before propagated to version 1.4.10 and 1.6.3. > > The proper fix would be to revert revision 39665, and bug 6472 has to be fixed > using another solution. Guys!! Its working well in my wireshark. I'm really sorry. I wrote correctly in my code but didn't submit the patch. I have just sent a c file which is truly correct.