Okay, not a bug, my bad.
I have the bitcoind instance set with a maxconnections limit. The code that executes a transaction (or the part that unlocks the wallet with the passphrase) just doesn't get reached somehow when Armory is in a state of constantly getting knocked on and then off the RPC connection to bitcoind. Restarted bitcoind less the maxconnection line in the conf and it's broadcasting fine. The thing is, I could've sworn that this worked in the past, but I've been unable to use Armory for a month or so, 4GB RAM wasn't cutting it any more etc, so I must be remembering wrong.
Sorry Alan, feel free to delete this if you don't want the sub cluttered.
Topic: Can't send from change-only wallet? (Read 700 times)
Definitely a bug. Send me your log file!
[email protected]
For reference, there is nothing special about change addresses. To the network, they look like any other addresses, and everything should work identically. However, given some abnormal behavior, like buttons or windows not behaving properly, there's most definitely some errors getting triggered and waiting for me in that log file!
[email protected]
For reference, there is nothing special about change addresses. To the network, they look like any other addresses, and everything should work identically. However, given some abnormal behavior, like buttons or windows not behaving properly, there's most definitely some errors getting triggered and waiting for me in that log file!
Wallet is entirely change received addresses, and it seems like I can't send the balance. No dialog box to confirm that the protocol doesn't allow this, the password window disappears and I end up back at the Send window underneath it. Bug? Feature?
Jump to: