Search content
Sort by

Showing 5 of 5 results by Quazzmo
Post
Topic
Board Armory
Re: Armory 0.96.4 release
by
Quazzmo
on 23/07/2018, 08:06:51 UTC
Looks like you're having a database issue. What were you on before upgrading to 0.96.4?

I was on 0.96.3

At first install attempt of 0.96.4 it couldn't write ArmoryDb.exe (as I recall, or something similar) as if it was still running in the background (I didn't check). Second install attempt didn't complain
Post
Topic
Board Armory
Re: Armory 0.96.4 release
by
Quazzmo
on 22/07/2018, 19:08:59 UTC
Hi,

Upgraded to 0.96.4 on win64
Nothing happens when I click "Send Bitcoins", except the following in my armorylog.txt:

2018-07-22 19:36:18 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3452, in clickSendBitcoins
  File "qtdialogs.pyc", line 4593, in __init__
  File "ui\TxFrames.pyc", line 150, in __init__
  File "ui\WalletFrames.pyc", line 232, in __init__
  File "ui\WalletFrames.pyc", line 347, in updateOnWalletChange
  File "ui\TxFrames.pyc", line 346, in setWallet
  File "ui\TxFrames.pyc", line 395, in setupCoinSelectionInstance
  File "CppBlockUtils.pyc", line 4140, in getCoinSelectionInstance
DbErrorMsg: >

(and I don't know how to attach the whole log file here...)
Post
Topic
Board Armory
Re: Armory 0.96 is out
by
Quazzmo
on 22/05/2017, 07:36:52 UTC
Quote
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!

There is no such thing. Offline mode is basically what you should be using to restore backups. If you're having issues, post your logs. Use pastebin.

Thanks goatpig, here's the partial armorylog.txt at the time of my first attempt to restore from the fragmented paper backup,
during which the "Restore from fragments" button remained greyed so I couldn't click it after typing in the codes:


2017-05-21 21:54 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-21 21:54 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-21 22:13 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 0
2017-05-21 22:13 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:16 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:16 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:25 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 0
2017-05-21 22:25 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:27 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:28 (INFO) -- ArmoryQt.py:4876 - New Block! : 467495
2017-05-21 22:28 (INFO) -- ArmoryQt.py:4884 - Current block number: 467495
2017-05-21 22:29 (INFO) -- ArmoryQt.py:4876 - New Block! : 467496
2017-05-21 22:29 (INFO) -- ArmoryQt.py:4884 - Current block number: 467496
2017-05-21 22:31 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:31 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 11718, in dataEnter
  File "qtdialogs.pyc", line 11898, in addFragToTable
  File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'

2017-05-21 22:33 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2017-05-21 22:33 (INFO) -- SDM.pyc:457 - Called stopBitcoind
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2017-05-21 22:33 (INFO) -- SDM.pyc:457 - Called stopBitcoind
2017-05-21 22:33 (INFO) -- SDM.pyc:463 - ...but bitcoind is not running, to be able to stop
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-21 22:33 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 5328, in closeEvent
  File "ArmoryQt.py", line 5415, in closeForReal
  File "twisted\internet\base.pyc", line 580, in stop
ReactorNotRunning: Can't stop reactor that isn't running.

2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe


Thanks for any suggestions!
Post
Topic
Board Armory
Problem restoring from fragmented paper backup
by
Quazzmo
on 21/05/2017, 22:50:52 UTC
Binaries:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96

changelog

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt

Notable changes:

1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features

Better description on the webpage: https://btcarmory.com/0.96.0-release/

Notes:

Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.

Thanks:

achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.

Enjoy =)





Happy to see Armory still moving forward, efforts are much appreciated here!
Has anyone successfully restored from a fragmented two of three paper backup with 0.96?
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
I'm trying to restore from a 2 of 3 fragmented paper backup, wallet version 1.35c with a SecurePrint code.
I type in my two fragments, but the "Restore from fragments" button remains disabled bottom right.
Am I doing something wrong, or is this a bug with a workaround perhaps?
Getting a little nervous as now running low on options for accessing my funds... A Windows update destroyed the PC holding my bitcoins!

Thanks for any help :-)
Post
Topic
Board Beginners & Help
Re: How to send BTCs from wallet generated by bitaddress.org?
by
Quazzmo
on 25/12/2013, 00:16:12 UTC
(warning Newbie post!)

Bottom line is ... Blockchain app on Android / iPhone is easy to use as it scans the paper QR codes printed from bitaddress.org

Today I was trying to do same to test some xmas presents.
Easiest way that worked for me in the end was:

1) For piece of mind do some testing
  a) Use bitaddress.org second tab to print a paper wallet or three (these are initially valid but empty)
    - I found photo paper was better, the font can be hard to read otherwise
  b) Use pretty much any bitcoin interface to send 0.002BTC (£0.84) to the "bitcoin address" on the "Load and Verify" bit of the paper wallet
    - That transaction is now on the bitcoin network, and verified after 10 minutes
    - I used "Bitcoin Wallet for Android" from bitcoin.org->Get started with bitcoin->Choose your wallet->Mobile wallets
  c) Install Blockchain app onto your smartphone (android, iPhone)
  d) Run Blockchain app and set up an account
  e) "Scan private key" and point camera at "Spend" QR square pattern on paper wallet
    - Blockchain tells you how much is in there (0.002BTC)
    - Blockchain offers to "Import" or "Sweep"
    - (not 100% sure here, but...) Sweep seems to take the money out of the paper wallet, so you lose a tiny transaction charge (0.0001BTC)
  f) Send your slightly-less-than 0.002BTC wherever you like, using "Pay To" from the blockchain app
    - Best send it to some other live wallet you have, so you can watch it turn up after a few mins
2) Print a paper wallet or three using second tab of bitaddress.org
3) Use the "Load and Verify" address to send some bitcoins to the paper wallet
4) Use Blockchain app for Android / iPhone to scan the "Spend" QR code, and "Sweep" the bitcoins out of the paper wallet
5) Use Blockchain app to do what you like with the bitcoins