Wireshark-bugs: [Wireshark-bugs] [Bug 12711] New: Wireshark doing Save As on the next day, does 
      
      
    
    
        
          | Bug ID | 12711 | 
        
          | Summary | Wireshark doing Save As on the next day, does not provide UI to do Save As | 
        
          | Product | Wireshark | 
        
          | Version | 2.0.5 | 
        
          | Hardware | x86-64 | 
        
          | OS | Windows 8.1 | 
        
          | Status | UNCONFIRMED | 
        
          | Severity | Normal | 
        
          | Priority | Low | 
        
          | Component | Qt UI | 
        
          | Assignee | bugzilla-admin@wireshark.org | 
        
          | Reporter | aschwabl@genetec.com | 
      
        
        Build Information:
Wireshark 2.0.5 (v2.0.5-0-ga3be9c6 from master-2.0)
Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 8.1, build 9600, with locale English_United
States.1252, with WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based
on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with
Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2), with 16325MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
Example using Wireshark on day 1, then stopping capture.
Then the next day (day 2), doing a "Save As" will not bring-up the Save As UI.
To recover the capture, I needed to access the user temp directory.
After restarting Wireshark Save As is ok.
Not sure if I selected the correct component "Qt UI"
         
      
      
      You are receiving this mail because:
      
      
          - You are watching all bug changes.