-
Notifications
You must be signed in to change notification settings - Fork 766
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
GUI v0.12 unable to connect to remote / local daemon (error std::bad_cast) #1261
Comments
+bug |
I run the daemon in my lan, the cli version successfully connects and syncs wallet with the blockchain. |
@badfiles: Which operating system are you using? |
same problem on Win64. daemon fails. log shows 2018-04-05 00:33:03.194 8536 WARN net.http src/wallet/wallet_errors.h:794 C:/msys64/home/vagrant/slave/monero-gui-win64/build/monero/src/wallet/wallet2.cpp:5610:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = gettransactions the local file does not exist. Also, monerod.exe is not included in the Win64 download. |
No issue here; running Arch linux version, connecting to version 0.12.0.0 node also running on Arch Linux. |
@memorie62 monerod.exe is definetely included, make sure no anti virus software removed it while unpacking |
I'm also affected. Running Xubuntu 16.04. |
Ubuntu 17.10 |
same on Ubuntu 16.04.4 LTS |
@CaptainPlanet77, @badfiles, @mbay1971: As last resort you can always run GUI v0.11 with daemon (
After block |
cli 0.12 works fine. and I don't need local daemon, I already have a running 0.12 daemon on another machine. |
same here. Ubuntu 17.10, v0.12 release binaries.
Same behavior for starting daemon in GUI or separately and for remote daemon. |
@erols - If the |
@dEBRUYNE-1 thanks. |
Unable to connect to daemon using monero-gui-v0.12.0.0 on Mint 18 confirmed |
Same here. Ubuntu 17.10. |
@badfiles did you need to open and run the CLI on another machine to connect to daemon. I see that CLI works, it is also working for me. Were you able to use this to make the GUI work? |
CLI from GUI package syncs well with my remote daemon. |
None of us did incur this bug whilst testing. Frankly, we were quite surprised too this bug was present. For anyone that is affected, could you please test the buildbot binary from here? https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/105 It should include a fix for this particular issue. |
@dEBRUYNE-1 buildbot binary also does not work. |
@notgiven688 - Same error in the log? |
I only get this error: |
|
@notgiven688 & @badfiles - are you using a local node or a remote node? |
remote node. I have no space for the whole blockchain on my laptop. |
@dEBRUYNE-1 local |
@dEBRUYNE-1, same issue with the fix on Linux Mint x64 |
That appears to have worked. What was the issue? I am guessing it wasn't RPC if there was some kind of compiler snafu. The last batch of binaries I may have neglected to fully test. I assumed we were only testing the GUI, and so swapped it out. This time, I copy-pasted the entire folder into my monero directory, replacing everything including monerod. I'll try whatever you like if you're interested. I've always wanted to help out with an open source project, and Monero is one of my favorites. |
@dEBRUYNE-1 , that works for me too now. Good work! some debug output with private data Xed: |
I'm very frustrated with this wallet, I need my money but I can not access it, only get badcast issue :( |
@MrPMontes Try the CLI or wait for updates. |
It finally works, thank you. |
same issue for me |
Works perfectly, Ubuntu 16 upgraded a while back, I look through the commit and can't figure out what's change? Is it only a change in the build environment? |
@RemiMorin - It's merely a change in the build environment. If I recall correctly, upgrading boost from 1.58 to 1.59 resolved the bad_cast issue. |
Build 201 fixes it for Ubuntu 17.10. If a new public release can be made, please. Also less tech-savvy users would like to use it. |
I agree that a new public build improve confidence and normalize the situation but you don't need to be tech-savvy. Just go on the the 201 build page you will see a link directly to the build archive: inside this archive you will find the release folder. This folder content is the same as an official public release. Just allow execution of the start-gui script and you are done. |
It's still an issue in 64 bit Linux. Just did a fresh install and this month-old bug is still happening. I can work around this but it takes a software guy like me to figure it out. Why is this still a problem? |
The latest client is fatally broken even though the cause has been known for weeks. Why there has been no update is beyond me. |
Please |
This is a build-related problem which will be fixed in the next point release. Meanwhile, you can use an unofficial binary built by buildbot https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/201 as suggested above #1261 (comment). |
edit: build 201 did resolve the |
@bananajamma Did you experience the |
+1 happening on Ubuntu 16.04 LTS. Broken even after clean wipe of data dir and wallet. imo XMR is probably the most underrated coin out here... but it's issues like this that have caused its lackluster performance as of late. |
same problem on Ubuntu 16.04 +1 |
Same problem here, Ubuntu 16.04. |
This still does not work, official website has old binary and the link from this thread is dead |
This link? https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/201 |
Yep, Can I download it from anywhere? |
This is the most recent build for the master which works for me: https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/472 |
Thanks @stoffu! |
Alright, this one seems fixed now. Unofficial release of 0.12.2: https://www.reddit.com/r/Monero/comments/8rkwyt/unofficial_release_of_gui_wallet_version_0122/ If you want the official releases, wait a bit. +resolved |
GUI v0.12.2.0, which includes a fix for this particular issue, has been released: https://www.reddit.com/r/Monero/comments/8vkx2g/gui_v01220_released/ |
Getting a few reports of people unable to connect to their own (local) node or remote node after upgrading to v0.12.0.0. Logs:
Case 1:
https://paste.fedoraproject.org/paste/QKowduN71M9OMENPNHX2Vg
https://paste.fedoraproject.org/paste/W3HZGq7O9~TTIfw3SSKJew
Reddit conversation: https://www.reddit.com/r/Monero/comments/89nn2p/monero_gui_v01200_lithium_luna_released/dws770b/
Case 2:
https://paste.fedoraproject.org/paste/dwXoiPEYE82lO5g7FB793Q
https://paste.fedoraproject.org/paste/pj3gZVLxvpcE5VWAvDsIXA
Reddit conversation: https://www.reddit.com/r/Monero/comments/89nn2p/monero_gui_v01200_lithium_luna_released/dwsh4fc/
EDIT: Three more Linux users affected here. The issue seems specific to Linux.
EDIT2: For anyone incurring this issue: As last resort you can always run GUI v0.11 with daemon (
monerod
) v0.12. Please see instructions below for using v0.11 and being sufficiently prepared for the upcoming scheduled network upgrade:After block
1546000
you should also ensure that your transaction uses ring size 7, otherwise it will be rejected by the network.EDIT3: Better overview of workarounds:
https://monero.stackexchange.com/questions/7999/linux-gui-v0-12-does-not-connect-to-local-or-remote-node-stdbad-cast-error
EDIT4: GUI v0.12.2.0, which includes a fix for this particular issue, has been released:
https://www.reddit.com/r/Monero/comments/8vkx2g/gui_v01220_released/
The text was updated successfully, but these errors were encountered: