|
Title: Electrum 2.6.4, something odd happened. Post by: Jhanzo on July 01, 2016, 03:13:08 AM It generates a change address when it shouldn't. I included what's left of my balance to the fee so the change address is not receiving anything.
This causes the rejected because of dust error when I try to Edit: Gone after I closed an reopened electrum. Couldn't take a screenie but looks like someone reported the same problem on github (https://github.com/spesmilo/electrum/issues/1839). Title: Re: Electrum 2.6.4, something odd happened. Post by: RealBitcoin on July 14, 2016, 07:42:13 AM Did you verify the integrity of the download?
https://electrum.org/#download Try reinstalling electrum and verify the integrity of the package, then try to reproduce this bug and see if it happens again. Maybe your files got corrupted or something, because it looks like a weird bug. Title: Re: Electrum 2.6.4, something odd happened. Post by: Jhanzo on July 14, 2016, 11:10:56 AM Did you verify the integrity of the download? https://electrum.org/#download Try reinstalling electrum and verify the integrity of the package, then try to reproduce this bug and see if it happens again. Maybe your files got corrupted or something, because it looks like a weird bug. I did. I downloaded, verified, and reinstalled again before trying to send out some btc to another wallet but it won't happen again. Also I've done 4 transactions (plus many unsigned tx when trying to reproduce it to take a screenshot) after I wrote this thread but never got the same problem again. Title: Re: Electrum 2.6.4, something odd happened. Post by: RealBitcoin on July 18, 2016, 03:58:03 AM Did you verify the integrity of the download? https://electrum.org/#download Try reinstalling electrum and verify the integrity of the package, then try to reproduce this bug and see if it happens again. Maybe your files got corrupted or something, because it looks like a weird bug. I did. I downloaded, verified, and reinstalled again before trying to send out some btc to another wallet but it won't happen again. Also I've done 4 transactions (plus many unsigned tx when trying to reproduce it to take a screenshot) after I wrote this thread but never got the same problem again. Idk, try reproducing the bug and report it on github, maybe there is a real bug here, maybe only the operating system is glitching. |