-
Notifications
You must be signed in to change notification settings - Fork 2.1k
MIST Dreadful "Ethereum node Connected" splash screen #3445
Comments
Welcome to the club of people that have a non working Ethereum Wallet, if you use light mode your are even more screwed. |
bah this wallet stinks! lol thank god for keystore -> MEW xD |
did yo uhave to re install ? |
I did not re-install, I just took out the ETH I had using MyEthereumWallet site. |
correct using MEW is alternative when the desktop wallet does not work |
But what about the project's contributers? Do they care less about the end user? Is that something ETH needs to suffer as coin/Contract..etc. ? If the wallet is broken, who will trust them with their money? |
Well looking at the issues being reported, there is a lot of issues to go over and try to correct. does take time and surely will fix it, hopefully in the next update |
Syncing will take a long time. Some of the people here seeing this issue are "stuck" just because they have not waited the full 7 days to sync. And some people may have waited the full seven days but another issue (connectivity, peer issues) have conspired against them. In these cases, the "stuck" experience is consistent with Mist's full node functionality and this issue is not actionable. HOWEVER, if you believe that Mist should start and open right away and then sync later, then please consider #3476. That issue is actionable and changes the user experience and the design of the Mist project. Please give us a comment or thumbs up there if you think that actionable solution helps you. |
My computer system is Windows 10, and I encountered the same problem. I think you can try to run the geth.exe which in the C:\Users\Username\AppData\Roaming\Ethereum Wallet\binaries\Geth\unpacked\geth.exe. After I runned it, the Mist started to download block and sync. |
Screenshot
MIST Get stuck trying to launch the wallet with the "Ethereum node connected" message.
Anybody know about it that already plans to fix it in the next version?
The text was updated successfully, but these errors were encountered: