05:08:15 <unhappymeal[m]> Sorry if this is the wrong channel but I have reached out everywhere and had no luck. I was wondering if any devs could help me out with this, please. I sent a transaction to a Monero account that got left pending for 2 days, I was freaking out because the other party had not received their funds, I read through some forum posts and said that the issue could be caused by my Monero GUI software being of date. I then updated my Monero
05:08:15 <unhappymeal[m]> GUI and the pending transaction switched to a failed transaction. On top of that, it reverted my Monero wallet to the balance it was at a couple of weeks ago which is around 3usd. The Monero is gone without a trace. Has anyone had this happen before? Is this a known issue?
05:37:49 <MajesticBank> happens sometimes, your monero is not lost
05:39:08 <MajesticBank> make sure that restore date goes before you started using that wallet
05:42:09 <selenze[m]> when u said, you updated the GUI...can you specify the version u were when u sent the monero and the new version you upgraded...and also is your blockchain synced as of now.
05:51:01 <unhappymeal[m]> i was on 0.17 something can't remember the exact version 
05:51:28 <unhappymeal[m]> I'm currently on the latest version 
05:51:31 <unhappymeal[m]> block chain is synced
05:52:41 <unhappymeal[m]> I downloaded it in December last year and haven't updated it since
05:52:48 <unhappymeal[m]> so it would be that version around that date
05:53:00 <selenze[m]> and is your balance intact...I mean is your transaction simply cancelled or you lost the amount you sent?
05:53:32 <unhappymeal[m]> I lost the amount that I sent
05:53:41 <unhappymeal[m]> was about 0.77 monero
05:54:06 <unhappymeal[m]> and what was left in my account when I updated the software
05:55:11 <selenze[m]> unhappymeal[m]: ???
05:57:47 <sech1> you didn't lose it, but you need to rescan your wallet
05:58:00 <unhappymeal[m]> Actually now that I remember I think I tried restoring the wallet to bring my funds back but it reverted my balance to how it was about 10 days ago
05:58:00 <unhappymeal[m]> around 3 usd
05:58:17 <unhappymeal[m]> i then put around 250 usd into my account when this all occured
05:59:05 <unhappymeal[m]> i put 250 dollars in first
05:59:09 <unhappymeal[m]> then this all occured
06:03:54 <selenze[m]> If I understood you correctly, you shouldn't have transacted at a lower version than what is currently...this is due to the hardfork. However, it seems your funds should not have get lost...I presume the blockchain would simply refuse to interact with the new version.
06:04:59 <unhappymeal[m]> I wasn't aware my software was out of date
06:05:05 <unhappymeal[m]> never prompted me to update or anything
06:06:08 <selenze[m]> from what I could think as of now...is for you to restore your block height from the GUI setting ...or if you do know your initial blockchain height...do that and then sync.
06:07:26 <unhappymeal[m]> to which height?
06:07:46 <unhappymeal[m]> the height it was at when I recieved all the monero
06:07:49 <unhappymeal[m]> ?
06:09:25 <sech1> the height when you received first transaction
06:12:04 <selenze[m]> if you have a modest cpu and SSD, you can start early from your first transaction or even the time (year or month) you started your monero activity in general. It won't take you much time to restore from an early height.
06:13:27 <selenze[m]> Having done that, if the problem still persists...your problem seems to related having to transaction with earlier Monero core version and you should ask the Devs or experts in such upgrade related issues later in the dev chatroom
06:36:47 <unhappymeal[m]> yeah I just tried that and just deleted the 3 dollars that was left in my account
06:57:04 <unhappymeal[m]> I restored it back and got my 3 dollars back lol
06:57:16 <unhappymeal[m]> but it just restored it to an empty wallet
06:57:26 <unhappymeal[m]> when i tried that so yeah
06:58:03 <unhappymeal[m]> i'll restore it to the start of the blockchain and see what happens
07:24:43 <selenze[m]> good to hear that.
09:59:15 <ghzoz64[m]> Hi,
10:01:08 <ghzoz64[m]> With the latest monero-gui version each time i get a error message in network status that said "wrong version", am using archlinux and didn't manage to solve this issue, i can't use monero since last update, could you help me please
10:02:55 <grumblemobile> Are you sure you're running the latest version for both wallet and node ?
10:03:05 <grumblemobile> Well, >= 0.18.0.0 at least.
10:03:23 <grumblemobile> The last number (and probably second to last) do not have to match exactly.
10:03:30 <ghzoz64[m]> Yes the latest of both 0.18.1.1
10:03:52 <grumblemobile> Did you by any chance let your wallet sync on an old version after the fork ?
10:04:23 <ghzoz64[m]> Nope
10:04:37 <grumblemobile> Hrm. Dunno then.
10:04:55 <grumblemobile> If you can use monero-wallet-cli, we can get a better idea. Is that something you can do ?
10:05:45 <ghzoz64[m]> Yes, sure but not at this time, am little bit busy
10:06:11 <grumblemobile> OK. So when you can, run it with your wallet and --log-level 2. see what message it gives you.
10:06:44 <ghzoz64[m]> ok, thank you grumblemobile
10:06:44 <grumblemobile> If somehting about max reorg height, you did let it sync with the wrong version, and you need to temporarily set a higher reorg height.
10:06:53 <grumblemobile> If something else that tell you what's wrong, then good.
10:07:22 <grumblemobile> Otherwise, check the log file for better info, and paste the relevant errors (with a couple dozen lines context) to paste.debian.net and post the link here.
10:07:53 <grumblemobile> Also I guess first make sure it's really using the node you think it's using.
10:08:04 <selsta> it's a bug in the new version
10:08:24 <selsta> we have an uninitialized variable that causes the wrong error message in some cases
10:09:07 <selsta> ghzoz64[m]: can you go to Settings -> Info and post your wallet mode?
10:09:08 <ghzoz64[m]> ok, so when you think bugs are going to be solved?
10:10:26 <ghzoz64[m]> Advanced mode localnode
10:10:47 <selsta> did you make sure your local node is started?
10:11:18 <selsta> Settings -> Node -> Start daemon
10:11:29 <ghzoz64[m]> Yes
10:12:38 <ghzoz64[m]> .When i open the gui, i've got a message "wrong version of the daemon connected"
10:13:48 <selsta> ignore the wrong version message for now
10:14:02 <ghzoz64[m]> ok
10:15:22 <selsta> like I said, there is a bug that the "wrong version" message can show up in case of other error messages, like being disconnected
10:15:32 <selsta> but the gui itself should work fine, I just tested it locally
10:15:42 <selsta> can you start the daemon manually from the command line?
10:17:33 <ghzoz64[m]> Problem is that the daemon is connected automatically in the gui always on stop daemon and can't stop it, i ve to force stop
10:19:39 <selsta> You have installed the GUI via arch?
10:19:48 <selsta> did this also install monerod somewhere?
10:22:31 <ghzoz64[m]> Yes, via arch, i also tested the official version and get the same bug
10:22:52 <ghzoz64[m]> monerod located in usr/bin
10:23:48 <selsta> ok, then can you simply start it from command line?
10:28:46 <ghzoz64[m]> sudo systemctl start monerod, ok it worked sync is working but now i can 't stop it via gui and the whole blockchain is downloaded to default location instead of my personal location, i can stop it via terminal
10:29:35 <selsta> you can set a custom directory with --data-dir
10:30:08 <selsta> ok, I see the issue now
10:30:48 <ghzoz64[m]> yes i know that, thank you for helping, hope i can use the gui again
10:31:50 <selsta> there are multiple ways to easily solve this, you can either downgrade to v0.18.1.0, start the daemon manually before starting the gui, or connect to a remote node
10:36:58 <ghzoz64[m]> Thank you selsta 
10:37:18 <selsta> ghzoz64[m]: I wrote a comment here https://github.com/monero-project/monero/issues/8583#issuecomment-1254840991
10:38:41 <ghzoz64[m]> 👍️👍️👍️