https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4027
Summary: Open Capture File dialog being canceled causes interface
to become unusable.
Product: Wireshark
Version: 1.2.2
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: leec100@xxxxxxxxxxx
Build Information:
Version 1.2.2 (SVN Rev 29910)
[Copyright notice]
Compiled with GTK+ 2.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, with GnuTLS 2.8.1, with Gcrypt 1.4.4, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 14 2009), with
AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1
beta5
(packet.dll version 4.1.0.1452), based on libpcap version 1.0.0, GnuTLS 2.8.1,
Gcrypt 1.4.4, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
--
Discovered while using v1.2.1 (SVN Rev 29141). Checked for newer version;
upgraded to v1.2.2 (SVN Rev 29910); bug remains persistent. First noticed it
happen in version v1.2.1.
Reproduction Steps:
1. Start Wireshark (for Win32) normally.
2. Once Wireshark has loaded and displaying the GUI, call the “Open Capture
File” dialogue by either (1) on the ‘welcome interface’ (listing common
operations), under the (central) “Files” section click the “Open (Open a
previously captured file)” option, or (2) via the keyboard command Ctrl+O.
(Note, however, that using either (1) “File”→“Open…”, or (2) the
toolbar button, does *not* cause reproduction (unless steps 2, 3, 4 are
followed as described, calling the “Open Capture File” dialogue via one of
the identified methods.)
3. Close/cancel/dismiss the “Wireshark: Open Capture File” dialogue box (by
any method).
4. Click anywhere within the Wireshark interface (even the toolbar/menu-bar)
— the “Wireshark: Open Capture File” dialogue box reappears (or is given
focus, if already open) upon each click (regardless of where that click is
performed within the interface).
No crash occurs, and no error is produced (in the GUI, at least).
Wireshark continues to respond, and can be commanded to exit gracefully.
If Wireshark is instructed to exit, and then restarted, the interface responds
as expected (unless the reproduction steps are performed).
Expected behaviour:
After the “Open Capture File” dialogue is canceled/closed, the interface
should behave as it would initially, prior to the “Open (Open a previously
captured file)” option is clicked.
If this state is *not* induced (by doing something other than the steps
described, such as performing a live capture), Wireshark works normally, as
expected.
If a capture file is actually opened/loaded is it displayed as expected.
If a loaded capture file is closed, returning to the ‘welcome interface’,
the interface behaves as expected (the bug is not reproduced).
If, even after performing other operations, steps 2, 3 and 4 are followed, the
bug is reproduced.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.