Wireshark-bugs: [Wireshark-bugs] [Bug 7649] New: File -> Open always closes existing capture fil
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 17 Aug 2012 05:55:43 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7649

           Summary: File -> Open always closes existing capture file
           Product: Wireshark
           Version: SVN
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: mmann78@xxxxxxxxxxxx


Build Information:
Version 1.9.0 (SVN Rev 44549 from /trunk)

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.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 Aug 16 2012), with AirPcap.

Running on Windows XP Service Pack 3, 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.12.18, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
--
I can't cancel out of opening a new Wireshark capture without losing the
existing file

Steps to reproduce:
1. Open pcap (Wireshark) file, say foo.pcap
2. Click File->Open
3. Hit Cancel button within File Open dialog


foo.pcap has already been unloaded, so canceling just leaves me with the
Wireshark welcome screen.

I can reproduce this on the SVN and v1.8.1, but not on 1.4.x (don't have
current access to 1.6.x).  I assume the desired behavior is to leave the
existing file open, but I'm not sure if other bugfixes have resulted in the
current behavior or the the Windows File Dialog is contributing to this
behavior.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.