-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Comments
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) |
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. |
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 : I'm goin to try the Git |
Note that what I am suggesting is not that you run Electrum from source and install dependencies yourself, |
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)
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. |
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 |
I am just having a hard time understanding where you got the DLL files from, and how come you have a run_electrum script. |
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 |
…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)
…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
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
. Even by python it just doesnt work.
The text was updated successfully, but these errors were encountered: