Topic: 0.96.4 RC1 - page 4. (Read 14225 times)

Coin Control still freezes GUI with 0.96.3.99

Ummm, try 0.96.4 RC1? You're posting in this thread, after all....

Coin Control freezing acting up again.  Clicking the button results in nothing happening.  Can't cancel out or close pop up window.  Using 0.96.2 expert mode in Debian VM.  Any news on fixing this?

Should be easy enough to reproduce anyways, just wanted to make sure it was with current code.

Compiled few days back when i had the other issues.
Now i sent already with coin control and that worked so guess compiling latest makes no sense for now as I wont be able to test the same again.

Is this with the latest state of testing?


It should work.

I'm trying to spend some mixed inputs but armory wont let me.


Selecting only 1 type of inputs works.
Isn't it possible to mix segwit with non segwit inputs?

I'm going to assume the situation has not change with the Python signer, right? Definitely something weird with the wallet state.


There are 3 possible states:

1) The ZC DB is corrupt and still shows the tx as unconfirmed, while they also appear as confirmed in the ledger. In this case, you can clear unconfirmed tx from the Help menu and restart Armory.

2) The ZC never actually mined. In this case, they may or may not be in the in a miner's mempool. You can just RBF these. You'll probably have to build the current state of testing as it has the RBF fixes in there. If you want signed builds, you'll have to wait till I'm done with this accursed BTG signer.

3) Your DB is stuck and can't see new blocks, therefor will never see these tx mined. You can check for this state by comparing Armory's top block (bottom right corner) to your network's top block. In this case, I'd need to see dbLog.txt before I can give you recommendations on how to proceed.

Woot!  Thanks, removing them, and with C++ signer, it worked.

Still have those 4 confirmed txs which Armory thinks aren't confirmed (and offers to bump fee).  I'll append tomorrow this one gets similarly stuck.

I have failed to reproduce the issue on my own. This has something to do with the state of your wallets. I'm going to need more data to figure out what's going. For starters, delete the .lmdb files in your datadir. They will reconstructed on the next run. See if that helps with the C++ signer.

I'll try to reproduce on my end and report back here.

(ERROR) TxFrames.py:925 - Problem sending transaction!
Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast
    ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2722, in signUnsignedTx
    cppsigner.signTx()
  File "/usr/lib/armory/CppBlockUtils.py", line 4165, in signTx
    return _CppBlockUtils.PythonSigner_signTx(self)
RuntimeError: failed signature
(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast
    ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2722, in signUnsignedTx
    cppsigner.signTx()
  File "/usr/lib/armory/CppBlockUtils.py", line 4165, in signTx
    return _CppBlockUtils.PythonSigner_signTx(self)
RuntimeError: failed signature

Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast
    ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2722, in signUnsignedTx
    cppsigner.signTx()
  File "/usr/lib/armory/CppBlockUtils.py", line 4165, in signTx
    return _CppBlockUtils.PythonSigner_signTx(self)
RuntimeError: failed signature

It looks like the Python signer is failing to populate the pubkey list of the unsigned tx object when it comes to imports. I'll investigate. For now, set yourself in expert user mode and try to manually pick the C++ signer at spend time, see if that fixes your issue.

Yes, 1RustyRX2oai4EYYDpQGWvEL62BBGqN9T didn't occur naturally

Hmm, it's the armory_0.96.3.99-gcc5.4_amd64.deb so I assume it's all included.  I'm not doing offline signing.

I don't need to reboot or anything?

Happy to hand you whatever you need via GPG email, if it helps.

Thanks,
Rusty.

What's vanity about it? Did you import a private key?

Edit:

Did you update your signer? Are you using mismatched versions between signer and online?

Same problem with my save and restored 1RustyR vanity wallet:

(ERROR) TxFrames.py:925 - Problem sending transaction!
Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast
    ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2705, in signUnsignedTx
    signerType=signer)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2886, in createAndInsertSignatureForInput
    DetSign, signerType=signerType)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1507, in createAndInsertSignature
    DetSign, signerType=signerType)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1425, in createTxSignature
    raise SignatureError('No PubKey that matches this privKey')
SignatureError: No PubKey that matches this privKey
(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast
    ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2705, in signUnsignedTx
    signerType=signer)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2886, in createAndInsertSignatureForInput
    DetSign, signerType=signerType)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1507, in createAndInsertSignature
    DetSign, signerType=signerType)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1425, in createTxSignature
    raise SignatureError('No PubKey that matches this privKey')
SignatureError: No PubKey that matches this privKey

Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 919, in createTxAndBroadcast
    ustxSigned = self.wlt.signUnsignedTx(ustx, signer=self.signerType)
  File "/usr/lib/armory/armoryengine/PyBtcWallet.py", line 2705, in signUnsignedTx
    signerType=signer)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2886, in createAndInsertSignatureForInput
    DetSign, signerType=signerType)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1507, in createAndInsertSignature
    DetSign, signerType=signerType)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1425, in createTxSignature
    raise SignatureError('No PubKey that matches this privKey')     
armoryengine.ArmoryUtils.SignatureError: No PubKey that matches this privKey

Ah indeed, the signer and online instance need to be in lockstep.

Guess this one:

But could be just because the signer is on an older version and the online node is on the current testing.

Do you have an error log for that last part?

I've setup on a clean new machine and now it works.
The signer still need to be fixed on my side as the signed TX is not recognized but i'm able to just broadcast the raw tx.