First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question
0

Lua: Error during loading: cannot open...

Dear experts in WireShark,

I have installed the latest version of WireShark in Windows 10. When I run the Wireshark, issued is the error message:

Lua: Error during loading: cannot open C:\Users\Username\Desktop\뺣낫듭땒\ㅅㅂ듟뜼궧 湲곗큹\WireShark\console.lua: Invalid argument

(I am a Korean and "뺣낫듭땒\ㅅㅂ듟뜼궧 湲곗큹" are Korean characters, most of which are NOT used ones in Korea.. The folder is non-existent.)

and cannot run.

I have tried with the privilege of Username and Administrator, but none succeeded.

Please let me know how to cope with this error.

Thank you in advance.

updated 2018-04-15 11:42:36 +0000
This post is a wiki. Anyone with karma >750 is welcome to improve it.
edit flag offensive 0 remove flag close merge delete

Comments

What is the install path of Wireshark, i.e. the directory that contains console.lua?

What locale is your system running in?

grahamb's avatar grahamb (2018-04-17 08:13:27 +0000) edit
more
  • delete

It is installed in the default directory, which is C:\Program Files\Wireshark.

And the locale is Korean.

Thank you.

gioir's avatar gioir (2018-04-17 09:26:58 +0000) edit
more
  • delete
add a comment see more comments

1 Answer

0

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.

Guy Harris's avatar
19.9k
Guy Harris
answered 2018-12-19 02:37:58 +0000
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer