-
-
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
wrong version #8583
Comments
Can you go to Settings -> Log and post the output of "status" ? |
Simple mode connects to a random remote node. If you connect to a remote node that is outdated (using v0.17) it will now say "wrong version". If you wait a bit it should connect to a new node. |
it wont let me drag and drop it here |
You should be able to copy paste it. |
yea tried that as well. Said something went wrong and it wouldnt let me. |
Can you make a screenshot? Or is that what failed? Then copy paste the text. |
Sent from Proton Mail mobile
https://www.reddit.com/r/Monero/comments/xk9ayu/monero_gui_problems/ipd4zr4?utm_medium=android_app&utm_source=share&context=3 I wrote down the status output in this reddit thread
-------- Original Message --------
…On Sep 21, 2022, 3:14 PM, selsta wrote:
Can you make a screenshot?
—
Reply to this email directly, [view it on GitHub](#8583 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMVPQWTV64MSOJ2H7KGEYKTV7NNAFANCNFSM6AAAAAAQSLOIIM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
It seems your daemon fails to start for some reason. Can you just set a custom remote node instead? I can give you instructions for it. |
Its a bootstrap simple wallet. The blockchain is downloaded to my hard drive. Even when i just try to connect to remote node same problem i have with local node. Wrong version |
Which remote node did you connect to? And did you switch to advanced mode for that? |
No i hit the icon in bottom left corner where it says switch to another public node when you hover your curser over it. |
Here is a picture of wallet
Sent from Proton Mail mobile
…-------- Original Message --------
On Sep 21, 2022, 3:30 PM, selsta wrote:
Which remote node did you connect to? And did you switch to advanced mode for that?
—
Reply to this email directly, [view it on GitHub](#8583 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMVPQWTSNGRLUIMKJW2HCLTV7NO6XANCNFSM6AAAAAAQSLOIIM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I sent you a picture with status on my cell phone to your email |
The easiest way to get things working is to follow the steps in this comment to connect to a remote node: monero-project/monero-gui#3989 (comment) |
How about my local node on my computer will i be able to use that? |
I mean thats why i downloaded the blckchain on my hard drive |
You can try to select Local Node and then press "Start Daemon". |
I, too, experienced the same problem of wrong version. My Linux distro is Debian 11.5.0 (64-bit) and I downloaded the latest version using the following link: https://downloads.getmonero.org/gui/monero-gui-linux-x64-v0.18.1.1.tar.bz2 I verified the hash of it using a GPG-signed list of hashes using the below link: https://www.getmonero.org/downloads/hashes.txt Next, I extracted the contents of monero-gui-linux-x64-v0.18.1.1.tar.bz2 to the /home directory. I launched it and typed in my password to the wallet. After a few seconds I received an error message at the top of the Monero GUI screen. It stated:
A few seconds later, two words Wrong version appeared under Network status in the bottom left corner of Monero GUI. In the Daemon Log these were the details:
I tried to disconnect it by going to Settings --> Node and clicking the orange button Stop daemon. Monero GUI refused to disconnect despite me clicking on Stop daemon many times. In the end, I had to click the X at the top right-hand corner of the GUI and then the grey button Force stop at least two times. Only then the stubborn Fluroine Fermi 0.18.1.1 exited/closed down. I deleted the un-zipped monero-gui-linux-x64-v0.18.1.1.tar.bz2 and rebooted my machine. I repeated the process of un-zipping monero-gui-linux-x64-v0.18.1.1.tar.bz2 to the /home directory and launching Monero GUI. The same error occurred. What happened next was I exited/closed down the stubborn Monero GUI, deleted the un-zipped monero-gui-linux-x64-v0.18.1.1.tar.bz2 and rebooted my machine. Fortunately I had not deleted the previous version. I un-zipped monero-gui-linux-x64-v0.18.1.0.tar.bz2 to the /home directory and launched it after typing the password. This time, there were two error mesages (white text, black background) near the bottom of Monero GUI. They were:
I hope that @selsta will find a solution to the bug soon. Meanwhile I will stick to the not-stubborn v0.18.1.0 version. Note: I have been using Monero GUI on Debian for more than two years now and never encountered such a serious bug before. |
We added a check that detects outdated nodes and wallets since a lot of people were connecting to outdated nodes, unfortunately due to a bug this breaks the daemon auto start / stop mechanic inside the GUI. We have a fix already and should have a new version out within the next days. In the meantime these are methods to work around it:
Edit: After doing more testing, the start / stop mechanic doesn't seem broken. Simple mode also seems to work for me. There's still the issue with "wrong version" showing up instead of "disconnected", but otherwise things seem to work here. |
Thank you for suggesting 3 workarounds but it's too late for me because I have reverted to using v0.18.1.0. Yes, there was a wallet rescan when I reverted to using v0.18.1.0 but the rescan didn't take much of my time. In any case, the rescan didn't corrupt data.mdb which is now 50.5GB (pruned). |
Actually I fixed this problem by uninstalling the monero GUI on my computer. Then sending wallet file to trash. Then I reinstalled the wallet GUI and restoring wallet file from trash folder. It worked perfectly and I was able to use local node stored on my hard-drive.
Sent from Proton Mail mobile
…-------- Original Message --------
On Sep 22, 2022, 7:06 AM, ch9PcB wrote:
***@***.***(https://github.com/selsta)
Thank you for suggesting 3 workarounds but it's too late for me because I have reverted to using v0.18.1.0.
Yes, there was a wallet rescan when I reverted to using v0.18.1.0 but the rescan didn't take much of my time. In any case, the rescan didn't corrupt data.mdb which is now 50.5GB (pruned).
—
Reply to this email directly, [view it on GitHub](#8583 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMVPQWQSIGSRKI643SB4FVLV7Q4TFANCNFSM6AAAAAAQSLOIIM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
You used the installer, monero-gui-install-win-x64-v0.18.1.1.exe, is that correct? |
I doubt reinstalling helps here. |
Totally agree with you. You ARE one of the developers of this software. How can @budmaster13 be able to fix things better than you? I noticed the post where you asked him to go to Settings --> Log and post the output of "status" and he gave many excuses. Moreover, he didn't tell you the operating system he used. He also referred to his post at Reddit/r/Monero titled Monero GUI problems in which he gave next to nothing feedback on the status. |
No status output makes sense when the daemon isn't started, which is happening with v0.18.1.1 |
First off I'd like to thank the developers for the quick response on this, but I feel that it does beg the question as to what sort of testing is done before releases. I'm curious how a bug as conspicuous as this can make it into a final release version without being noticed a single time. Does this particular bug in gui v0.18.1.1 affect everyone trying to use a local daemon on all platforms? |
It does not affect using a local node directly, it affects the start / stop mechanic. If someone starts the daemon manually everything works fine. The bug was an uninitialized variable in one part of the code (that unfortunately the compiler didn't warn about) that causes a bug somewhere completely else. I did do testing, but it was in remote node mode, so I didn't see the broken start / stop mechanic. I personally don't have the resources to test every GUI feature before every release. Edit: To add to this, I always start my daemon manually since I use master branch, which again caused that I didn't see the bug. |
How was it that I was able to provide a Daemon Log?
I understand that you are contributing your own time and resources to this project. Any bug -big and smal- don't faze me. I wish to take this opportunity to thank you for your hard work. |
@ch9PcB I'm don't know, could have been a timing thing where the daemon started before it got into the buggy wrong version mode. |
I'm getting the same invalid version error, using my own node. Remote node version:
That's running on debian and was installed from source 2 days ago. That's running on Arch and was installed with The "Type a command box" in the GUI's
Uninstalling and re-installing the GUI with
|
@ki9us So you are using Advanced mode (remote node)? Can you try to connect to one of these
to make sure it is not a network issue with the node you have? |
That worked! It was my fault: port 18081 was closed. Well it was unblocked but So for me it just was a matter of a misleading error. BTW do you know how to set this for ipv6? I tried |
This "Wrong version" bug impacts people using v0.18.1.1 in the following ways:
All the above should be fixed in the next release. The code is here and here available for testing. Personally I was extremely thorough in my GUI tests this time around and will be more thorough in testing the GUI in the future.
This was a valid question. First of all I wrote the code. The mistake originated with me. I take responsibility for this. I tested every code path I wrote and tested every possible daemon configuration pointing my CLI wallet to:
There were additional combinations and permutations I tested making sure to hit all pieces of the code I impacted in the CLI wallet, but this should give you an idea of the testing I did. I also ran tests with the GUI and RPC wallet myself, but was not as extensive in those tests. Everything I did test worked as expected, and I spent a solid number of hours testing. As @selsta said, the primary bug was an uninitialized variable. Here it was:
Since @selsta is always on top of and helpful in testing; various community members step up to help testing all the time as well. In an ideal world, all Monero wallets would have dedicated QA testers on each release who test all features and bug fixes on different systems before every release. |
Hello Justin We don't blame you or ask that you admit your responsiblity for any errors that have happened or will ever happen to the code that you wrote and will write in the future. We acknowledge that you are volunteering your spare time and limited resources to this project of your own free will. We thank you that, in spite of your work and family commitments, you decide to advance this project along. |
Fix has been merged, will be included in v0.18.1.2 |
v0.18.1.2 is out https://www.getmonero.org/downloads/ |
It's a simple mode with fullnode bootstrap
Sent from Proton Mail mobile
…-------- Original Message --------
On Sep 21, 2022, 3:07 PM, selsta wrote:
Simple mode connects to a random remote node. If you connect to a remote node that is outdated (using v0.17) it will now say "wrong version". If you wait a bit it should connect to a new node.
—
Reply to this email directly, [view it on GitHub](#8583 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMVPQWSZ4AG5TSG6NUQ6M73V7NMG7ANCNFSM6AAAAAAQSLOIIM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@budmaster13 make sure to update to v9.18.1.2 |
still doesn't work on Mac. |
@bitflorist You have to explain what you are trying to do and what exactly doesn't work. Also post which wallet mode you are using in Settings -> Info. |
Daemon wont connect to GUI says using wrong version but i have latest version GUI version: 0.18.1.1-unknown (Qt 5.15.6)
Embedded Monero version: 0.18.1.1-unknown
Wallet path: /home//Monero/wallets
Wallet restore height: 2686804
Wallet log path: /home/.bitmonero/monero-wallet-gui.log
Wallet mode: Simple mode (bootstrap)
Graphics mode: OpenGL
I have used this wallet several times after fork with no issues. Now its saying im using wrong version.
The text was updated successfully, but these errors were encountered: