Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Please let me know how to cope with this error.

Wait for the next Wireshark release and update to that. This is probably bug 15118, which should be fixed in the next 2.6.x and 2.4.x releases, as well as in the next 2.9.x development release and the 3.0 release.

The next 2.6.x and 2.4.x releases should be available early in 2019; the 3.0 release should be available at the end of January 2019.

There's also another bug that should also be fixed in those releases; it's bug 15367, which causes pathnames with non-ASCII characters not to be displayed correctly in message dialogs on Windows. That would probably explain why the pathname in the message includes the characters "뺣낫듭땒\ㅅㅂ듟뜼궧 湲곗큹" - it's probably incorrectly displaying the pathname. That bug and bug 15118 have similar underlying causes.

If you don't want to wait for the new releases, you could try downloading one of the automated Windows builds for 32-bit Windows or for 64-bit Windows. Download the most recent "Wireshark-win32-2.6.6rc0-NN-gxxxxxxxx.exe" or "Wireshark-win64-2.6.6rc0-NN-gxxxxxxxx.exe" file, and run it; it will install the version from the automated build. Those builds include whatever fixes have been put into those release streams; they may have other issues. I'm not sure whether the automatic update mechanism will upgrade to the new 2.6.x release when it's available, so you may have to download it and install it yourself. You should not run any of those automated builds once the next 2.6.x release is available; you should upgrade to the release.