Multibit HD double transaction sent

[VirosaGITS]

This happened;
https://i.imgur.com/wsM3cJq.png?1
https://blockchain.info/tx-index/3d049c1cc0a8077e12911b7bbb75c2662a2ebf82325d0ccd2e578b545c74010d

"Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105195339, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=1b0413d81ebe883006f4257bf61209904f950a659e6836eb38925e78ac3c601d, getVersion()=1, getSize()=1700, toString()"

Simply by clicking the send button a few time while the wallet was not responding. The label was replaced by the automatically generated info seen there.
It was instantly rejected by blockchain.info but still i don't think this is intended to happen. Not a big deal but i thought i'd report it anyways.

[shorena]

Sounds like the ongoing malleability attack rather than an issue with too many clicks on a button.

The TX IDs are different. Use the "repair" function of MB to get the wallet back to normal once one of the transactions is confirmed.

[VirosaGITS]

Sounds like the ongoing malleability attack rather than an issue with too many clicks on a button.

The TX IDs are different. Use the "repair" function of MB to get the wallet back to normal once one of the transactions is confirmed.

Well the second transaction was done after the original/legit transaction. It will never confirm, while the original one confirmed before i had the time to post this. Its still working as normal. You mean it would remove the bad transaction from the list?

[shorena]

Sounds like the ongoing malleability attack rather than an issue with too many clicks on a button.

The TX IDs are different. Use the "repair" function of MB to get the wallet back to normal once one of the transactions is confirmed.

Well the second transaction was done after the original/legit transaction. It will never confirm, while the original one confirmed before i had the time to post this. Its still working as normal. You mean it would remove the bad transaction from the list?

Its not set in stone that the first will always confirm, its possible that the 2nd confirms... anyway. Yes, it should remove the conflicting transaction without confirmation from your wallet and show the correct balance.

[everaja]

Dont Worry you wont lose your coins twice as this transaction will not confirm!!
Just Chill !!

[VirosaGITS]

Sounds like the ongoing malleability attack rather than an issue with too many clicks on a button.

The TX IDs are different. Use the "repair" function of MB to get the wallet back to normal once one of the transactions is confirmed.

Well the second transaction was done after the original/legit transaction. It will never confirm, while the original one confirmed before i had the time to post this. Its still working as normal. You mean it would remove the bad transaction from the list?

Its not set in stone that the first will always confirm, its possible that the 2nd confirms... anyway. Yes, it should remove the conflicting transaction without confirmation from your wallet and show the correct balance.

Like i said and as you can see on the picture and info i posted, the transaction was instantly rejected, it was completely invalid, the balance was not spent twice and there was nothing to confirm.

I'm just posting because the dev might want to know that the software can send a duplicate transaction under certain circumstance. It is a harmless bug but a bug nontheless.

Dont Worry you wont lose your coins twice as this transaction will not confirm!!
Just Chill !!

Dont worry, i didn't lose any balance or fear anything. Like i said the transaction was instantly rejected by the node. You can see that by reading the first post. So you don't need to worry about me worrying. Just Chill !!