Problem with Wireshark 2.2.0 (v2.2.0-0-g5368c50 from master-2.2) on Windows 7, 64-bits When started Wireshark by clicking on file I got an error message: The file "xxx.pcap" doesn't exist Then I was transferred to the File open menu. From that menu the file was opened correctly. asked 21 Sep '16, 04:41  Christer G showing 5 of 6 show 1 more comments |
2 Answers:
Can you try one of the 2.2.1 automated builds? There was a regression in 2.2.0 which kept Wireshark from handling multibyte characters correctly on the command line (which includes files opened from Windows Explorer). It will be fixed in 2.2.1. answered 21 Sep '16, 13:44  Gerald Combs ♦♦ I observed exactly the same symptoms. In the file path I had these non-ASCII characters: "á" and "í". A new build of 2.2.1 (Wireshark-win64-2.2.1rc0-48-g85abe17.exe) as suggested by Gerald Combs resolved the problem. (25 Sep '16, 15:42) pabouk |
OK, based on the comments (thanks for the responses) it looks like there's a problem if the full path of the opened-from-the-OS-file-browser file includes non-ASCII characters. This could be lumped into bug 1827 but it's probably/hopefully simpler than that never-ending bug. I'd suggest opening a separate bug report for this particular case. answered 21 Sep '16, 10:48  JeffMorriss ♦ |
(I assume you mean you're clicking on a file in Windows explorer?)
It works fine for me.
By chance are there any non-ASCII characters in the file or path name? (If you're not sure then just cut-n-paste the full path name here.)
One of the file names is Melsec_691_MsgId_1.pcap Another is 20130321.pcap With another extension 20130930.pcapng
The "clicking" is, as you presumed, in Windows Explorer. The folders have an underscore in their name.
Your "answers" has been converted to comments as that's how this site works. Please read the FAQ for more information.
And there's nothing in full path (probably including your user name) that's not ASCII? (Just checking...)
Yes there were. Thanks for the help.