| Bug ID |
8224
|
| Summary |
Wireshark can incorrectly interpret the export filename as the same as the current filename.
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.9.0 (SVN Rev 47120 from /trunk)
Compiled (64-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_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, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Jan 16 2013), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap, GnuTLS
2.12.18, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 10.0 build 30319
--
When exporting packets to a new file, Wireshark incorrectly thinks the export
filename is the same as the current filename if you first select the current
filename with the mouse (to avoid typing the whole thing), and then edit the
file name.
If you manually type the entire export filename, then Wireshark is happy.
(This bug was discovered while testing bug 8223. Read the 3rd paragraph of
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8223#c2 for a specific
example.)
You are receiving this mail because:
- You are watching all bug changes.