Wireshark-bugs: [Wireshark-bugs] [Bug 9635] New: Close program problem

Date: Tue, 14 Jan 2014 11:40:55 +0000
Bug ID 9635
Summary Close program problem
Classification Unclassified
Product Wireshark
Version 1.10.5
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 1.10.5 (SVN Rev 54262 from /trunk-1.10)

Copyright 1998-2013 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.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Dec 19 2013), with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57, with 1982MB of physical memory.

Built using Microsoft Visual C++ 10.0 build 40219
--
Upon closing WS, you are given the option to Save the capture.  Upon getting
the Save dialog window, you are given the option to Cancel the save.  WS then
ends.  What I believe it should do with a Cancel here is close the Save dialog
window and return to the WS GUI.  Then the user can choose the 'Quit without
Saving' button.  What happened to me was I decided to do more investigation
with the captured data in the interface before actually closing the interface,
but got the rude awakening that the program closed anyway rather than going
back to the GUI.  Thanks.


You are receiving this mail because:
  • You are watching all bug changes.