Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal script error #6601

Open
lumor367 opened this issue Sep 17, 2020 · 9 comments
Open

Fatal script error #6601

lumor367 opened this issue Sep 17, 2020 · 9 comments

Comments

@lumor367
Copy link

Message error: "Failed to execute script run_electrum" . I've already googled all the options to fix this issue. I've upgraded the electrum for the last one 4.03. My windows 10 is also updated in last version as also the Python 3.8 till flashes, codecs, drivers, my pc hardwares, everything is updated, and restarted my pc several times. As also tried Electrum previous versions but still not opening it
elecerror

. Even by python it just doesnt work.

@SomberNight
Copy link
Member

Could you try running Electrum in a console/terminal, so that it can print a detailed error?

Unfortunately, on Windows, Command Prompt (cmd) does not work for this, as Electrum is compiled as a "windowed" application instead of a "console" application, so you would need to install a more powerful console.

Specifically, MinTTY would work. See instructions here: #2592 (comment)

@SomberNight
Copy link
Member

Alternatively, I could create a custom build of Electrum for you that is built as a "console" application, if you are willing to run that.

@lumor367
Copy link
Author

Could you try running Electrum in a console/terminal, so that it can print a detailed error?

Unfortunately, on Windows, Command Prompt (cmd) does not work for this, as Electrum is compiled as a "windowed" application instead of a "console" application, so you would need to install a more powerful console.

Specifically, MinTTY would work. See instructions here: #2592 (comment)

Yeah, I tried run in Powershell, in first moment I could to install the requirements such as symmetric ciphers pycryptodomex, but Im having problem with libsecp256k1. The install of libsecp256k1 occurs very well, but when I try to ./run_electrum then just shows this :
" \libsecp256k1-0.dll' (or one of its dependencies). Try using the full path with constructor syntax."), FileNotFoundError("Could not find module 'libsecp256k1-0.dll' (or one of its dependencies). Try using the full path with constructor syntax.")]
Error: Failed to load libsecp256k1.

I'm goin to try the Git

@SomberNight
Copy link
Member

Note that what I am suggesting is not that you run Electrum from source and install dependencies yourself,
but rather that you use a "MinTTY" terminal to run the same Electrum binary you have already downloaded.

SomberNight added a commit to SomberNight/electrum that referenced this issue Sep 17, 2020
The "setup" Windows binary we distribute allows users to "install" Electrum
on their system. The distributable is created by NSIS. During
installation a bunch of files will get unpacked in %programfiles(x86)%/Electrum,
including an "inner" exe that will be the entrypoint for the user to start
the application. A shortcut is also created for the inner exe.

With this change, there will now be two inner EXEs. One the same as before,
the other with a "-debug" suffix in its name. The debug exe is built as a
"console" application (as opposed to a "windowed" application), so when
launched via double-click a black console window would appear; and also
importantly stdin/stdout are handled properly for it (unlike for "windowed"
programs). (see spesmilo#2592)

There will not be a shortcut or similar for the debug exe; it would just
be there as a debugging option we can instruct users to use when needed.
In particular early crashes during startup are hard to debug without
stdout/stderr. (see e.g. spesmilo#6601)
@lumor367
Copy link
Author

Note that what I am suggesting is not that you run Electrum from source and install dependencies yourself,
but rather that you use a "MinTTY" terminal to run the same Electrum binary you have already downloaded.

Finally it opened: I've noticed that some dll files didnt into electrum subfolder as they are into Electrum main setup folder. I just copied all dll files and pasted into subfolder electrum, an then ./run. Finally works.

@SomberNight
Copy link
Member

So are you running from source then? How exactly did you fix it?

Have you tried running the official binary with MinTTY? Do you have logs from that?

@lumor367
Copy link
Author

So are you running from source then? How exactly did you fix it?

Have you tried running the official binary with MinTTY? Do you have logs from that?

As I said before, I just copied all dll files from main setup fodlder into subfolder electrum then ./run_electrum in powershell

@lumor367 lumor367 reopened this Sep 19, 2020
@SomberNight
Copy link
Member

SomberNight commented Sep 19, 2020

I am just having a hard time understanding where you got the DLL files from, and how come you have a run_electrum script.
Specifically, you would only have a run_electrum script if you were running from source; and re the DLL files if you built them yourself they would already get placed in the expected location. That leaves me to believe that you are running from source but you copied the DLL files from the official release binary (presumably the setup/installer exe).

@lumor367
Copy link
Author

Thats it!!! : "> That leaves me to believe that you are running from source but you copied the DLL files from the official release binary (presumably the setup/installer exe)."

SomberNight added a commit that referenced this issue Oct 12, 2020
…6603)

The "setup" Windows binary we distribute allows users to "install" Electrum
on their system. The distributable is created by NSIS. During
installation a bunch of files will get unpacked in %programfiles(x86)%/Electrum,
including an "inner" exe that will be the entrypoint for the user to start
the application. A shortcut is also created for the inner exe.

With this change, there will now be two inner EXEs. One the same as before,
the other with a "-debug" suffix in its name. The debug exe is built as a
"console" application (as opposed to a "windowed" application), so when
launched via double-click a black console window would appear; and also
importantly stdin/stdout are handled properly for it (unlike for "windowed"
programs). (see #2592)

There will not be a shortcut or similar for the debug exe; it would just
be there as a debugging option we can instruct users to use when needed.
In particular early crashes during startup are hard to debug without
stdout/stderr. (see e.g. #6601)
reddink pushed a commit to reddcoin-project/electrum-redd that referenced this issue Nov 10, 2020
…pesmilo#6603)

The "setup" Windows binary we distribute allows users to "install" Electrum
on their system. The distributable is created by NSIS. During
installation a bunch of files will get unpacked in %programfiles(x86)%/Electrum,
including an "inner" exe that will be the entrypoint for the user to start
the application. A shortcut is also created for the inner exe.

With this change, there will now be two inner EXEs. One the same as before,
the other with a "-debug" suffix in its name. The debug exe is built as a
"console" application (as opposed to a "windowed" application), so when
launched via double-click a black console window would appear; and also
importantly stdin/stdout are handled properly for it (unlike for "windowed"
programs). (see spesmilo#2592)

There will not be a shortcut or similar for the debug exe; it would just
be there as a debugging option we can instruct users to use when needed.
In particular early crashes during startup are hard to debug without
stdout/stderr. (see e.g. spesmilo#6601)

(cherry picked from commit 653a24a)

# Conflicts:
#	contrib/deterministic-build/electrum-redd-locale
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants