Armory 0.96 is out

[goatpig]

When I try to send BTC I get "coin selection failed with targetval > value" error with "Change Address Type" set to Auto. Force to P2PKH works however.
Armory 0.96 and Bitcoin core 0.14.0

What value were you trying to spend in relation to your utxo value?

[1714130045]

1714130045

[1714130045]

1714130045

[1714130045]

1714130045

[SimonBelmond]

Code:

2017-05-07 22:31 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-07 22:31 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-07 22:31 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-07 22:31 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\Ben\\AppData\\Roaming\\Bitcoin\\', '-dbcache=2000']
2017-05-07 22:31 (INFO) -- SDM.pyc:443 - PID of bitcoind: 4316
2017-05-07 22:31 (INFO) -- SDM.pyc:444 - PID of armory:   6476
2017-05-07 22:31 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '6476', '4316']
2017-05-07 22:31 (WARNING) -- ArmoryQt.py:1804 - DB is already running
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-07 22:31 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-07 22:31 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-07 22:31 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-07 22:32 (ERROR) -- qtdialogs.pyc:5840 - Error showing TxOut
Traceback (most recent call last):
  File "qtdialogs.pyc", line 5838, in showTxOutDialog
  File "qtdialogs.pyc", line 6069, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-07 22:33 (ERROR) -- qtdialogs.pyc:5840 - Error showing TxOut
Traceback (most recent call last):
  File "qtdialogs.pyc", line 5838, in showTxOutDialog
  File "qtdialogs.pyc", line 6069, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-07 22:33 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 3490, in clickReceiveCoins
  File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'ArmoryMainWindow' object has no attribute 'Warning'

I think this was added when I tried the other method:

Code:

2017-05-07 22:36 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 1541, in getNewAddress
  File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'DlgWalletDetails' object has no attribute 'Warning'

[goatpig]

Seems like some GUI edge case, will investigate.

[SimonBelmond]

Just found another thing. Transaction info, right clicking on the sender and choosing "copy sender address" gives me this if the sender is me:

Code:

Wallet: "Smart Cold Storage (Watch) (Watc" (1XXXXXX...)

It seems to work on the recipient section

[goatpig]

Just found another thing. Transaction info, right clicking on the sender and choosing "copy sender address" gives me this if the sender is me:

Code:

Wallet: "Smart Cold Storage (Watch) (Watc" (1XXXXXX...)

It seems to work on the recipient section

You mean it should just be the address, not the whole verbose?

[SimonBelmond]

Just found another thing. Transaction info, right clicking on the sender and choosing "copy sender address" gives me this if the sender is me:

Code:

Wallet: "Smart Cold Storage (Watch) (Watc" (1XXXXXX...)

It seems to work on the recipient section

You mean it should just be the address, not the whole verbose?

Yes that is at least what I would expect from a copy address feature. As I mentioned it works fine for receiver addresses that I control, only sender addresses I own afdected.

[2NIzko]

Ubuntu 16.04 with armory_0.96-gcc5.4_amd64.deb, after doing upgrade from 95.1 to 96, i start armory and it doesnt even start up, the icon would flash a few times and the logs wont even write anything.

When i start armory from terminal, i get this: Illegal instruction (core dumped)

Was i supposed to completely remove 95.1 ?

[2NIzko]

So i sorted that out by removing armory_0.96-gcc5.4_amd64.deb and installing armory_0.96-gcc4.7_amd64.deb

Then when i start armory i get:

(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
-ERROR - 1494239616: (WalletManager.cpp:78) Failed to open wallet with error:
missing main wallet entry
Illegal instruction (core dumped)


I think this is because in version 95.1 i had an unconfirmed transaction because of a low fee given, a mistake i made.  I knew that clear all unconfirmed did not work in armory 95.1, so i upgraded now to run "clear all unconfirmed" but as soon as i open armory it throws that error about the entry.  Anything i can do to get this fixed @goatpig?
I also see the wallet being locked in the folder to "_wallet.lmdb-lock"

I tried removing the wallet or moving it in a temp dir, started up armory again and i see this error message now:

(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
Illegal instruction (core dumped)

After which i went back into .armory folder and deleted databases and settings to start from scratch.  Armory then opened with welcome message etc.

It started scanning and then during 68% it got stuck so i looked in .bitcoin/debug.log and saw this error:

-INFO  - 1494241552: (DatabaseBuilder.cpp:268) parsed block file #587
-INFO  - 1494241554: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 1494241554: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1494241554: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

So i started up armory again and it is busy scanning now but stuck at preparing databases.. looked in .armory/dbLog.txt and it still scanning but its just not showing it in the GUI anymore.  So currently im waiting for this to finish

can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction 

[goatpig]

Anything i can do to get this fixed @goatpig?

Build the code yourself. This is some issue with the autotoolized version of cryptopp that relies on more SSE than older machines can handle. I'm trying to fix this for 0.96.1. For the mean time your best bet is to build 0.96 directly on your machine.

can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction  Huh

Import in offline mode first then sync in online mode. If you want to wipe the ZC, delete the following files in your DB folder:

Code:

zeroconf
zeroconf-lock

[2NIzko]

Anything i can do to get this fixed @goatpig?

Build the code yourself. This is some issue with the autotoolized version of cryptopp that relies on more SSE than older machines can handle. I'm trying to fix this for 0.96.1. For the mean time your best bet is to build 0.96 directly on your machine.

can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background.  please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction  Huh

Import in offline mode first then sync in online mode. If you want to wipe the ZC, delete the following files in your DB folder:

Code:

zeroconf
zeroconf-lock

@goatpig
I tried doing what you said above, even in offline mode i tried to import but the gui crashes and theres nothing written in the logs about that issue.
I even deleted the zeroconf-lock files.

when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

I dont know why these files are auto created?

I uninstalled armory 96.0 and reinstalled the old version, seeing everything sync up again, the entry that was unconfirmed is no longer there anymore which is a good thing.
The bad thing is that it doesnt seem like wallet importing works in 96.0.

Im going to recreate a new empty wallet from the old armory and try import that into the new armory and il get back to you on that.

[goatpig]

when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

These are watching only copies of the python wallet for the new code to run off of. You can delete these all you want, but 0.96 will recreate them on the fly if they are missing. Earlier versions don't use these files.

[2NIzko]

when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

These are watching only copies of the python wallet for the new code to run off of. You can delete these all you want, but 0.96 will recreate them on the fly if they are missing. Earlier versions don't use these files.

Ok, well i created a test wallet in 95.1 and upgraded to 96.0, i open armory with test wallet files inside folder already and it will create these watch only wallets but as soon as the GUI begins to start up, it crashes.

I especially tried this with offline armory, to import digital backup or even from paper backup and as soon as i import, it crashes, i open offline armory again and the wallet didnt import, yet its still in the folder.
I checked the armorylog.txt file and it says this before the crash:
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2172 -    Wallet (35Qpf31Yj):   "Test                            "   (Encrypted)
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes

crashes just after that.

Im not sure why this is happening even with brand new wallets.  The other thing is that i tried doing a test backup on both wallets and it crashes the gui on that too.

[2NIzko]

I also noticed something weird (which i dont know if this might be the cause): between the two gcc armory versions, the 4.7 one was the one that ive been trying to get to work with the wallet files (which means it opens up).
However when checking why armory_0.96-gcc5.4_amd64.deb wasnt opening at all. Everytime i tried opening it, i saw in syslog this error line:

traps: python2[29095] trap invalid opcode ip:7f5a01402ec0 sp:7ffeddbf0808 error:0 in _CppBlockUtils.so[7f5a00f4d000+6a9000]

And when i do gcc -v in terminal to see my version of gcc, it prints that i have the latest 5.4:
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)

 

[goatpig]

What CPU are you using? The 5.4 version is built with a lot of x86 instructions that may not be available on your hardware.

[2NIzko]

What CPU are you using? The 5.4 version is built with a lot of x86 instructions that may not be available on your hardware.

Im using Intel Core i7 CPU 920.

Can you tell me what do you think the issue might be when the new version of armory is preventing wallets from being opened that were created with 95.1 like i described above?  Is it a bug?

[goatpig]

I would have to see a full log file, both armorylog and dbLog

[shaqattaq]

Hi Goatpig et al, thanks for all your hard work with this release.

I believe I'm experiencing the same problem as neosatus.

ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."

I have updated both Armory and Core (14.1).

Here's the dbLog for the latest crash, ArmoryDB.exe appears to continue to run.

Code:

Log file opened at 1494297575: C:\Bitcoin DBs\Armory DB/dbLog.txt
-INFO  - 1494297575: (..\main.cpp:23) Running on 2 threads
-INFO  - 1494297575: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1494297575: (..\BlockUtils.cpp:907) blkfile dir: C:\Bitcoin DBs\Bitcoin Core\blocks
-INFO  - 1494297575: (..\BlockUtils.cpp:908) lmdb dir: C:\Bitcoin DBs\Armory DB\databases
-INFO  - 1494297575: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1494297576: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1494297577: (..\BDM_Server.cpp:996) registered bdv: 7471bf47422af7fc355a
-INFO  - 1494297593: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1494297596: (..\DatabaseBuilder.cpp:208) Found 465842 headers in db
-INFO  - 1494297601: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508411bytes
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494297602: (..\Blockchain.cpp:242) Organizing chain 
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.968s
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465454 to #465453
-INFO  - 1494297602: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1494297602: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.019s
-INFO  - 1494297602: (..\DatabaseBuilder.cpp:160) init db in 26.789s
-INFO  - 1494297602: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking 
-INFO  - 1494297604: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN  - 1494297636: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1494297641: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1494297685: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN  - 1494297687: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN  - 1494297715: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN  - 1494297715: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-ERROR - 1494298924: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1494298924: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO  - 1494298926: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN  - 1494298991: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO  - 1494299046: (..\BDM_Server.cpp:1025) unregistered bdv: 7471bf47422af7fc355a
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 75 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 80 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 85 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 90 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 95 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 100 zc parser threads
-WARN  - 1494299176: (..\BDM_supportClasses.cpp:1891) running 105 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 110 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 115 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 120 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 125 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 130 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 135 zc parser threads
-WARN  - 1494299263: (..\BDM_supportClasses.cpp:1891) running 140 zc parser threads

armorylog has this entry at the time of the crash:

(WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing

Thanks for any assistance.

Cheers.

[achow101]

Can you also post the armorylog.txt?

[shaqattaq]

Sure thing, thanks for the reply:

Code:

2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1255 - 
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1256 - 
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1257 - 
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1262 -    Armory Version        : 0.96
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1263 -    Armory Build:         : a3d01aa722
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1264 -    PyBtcWallet  Version  : 1.35
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1266 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1267 -    User home-directory   : C:\Users\xxx\AppData\Roaming
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1268 -    Satoshi BTC directory : C:\Users\xxx\AppData\Roaming\Bitcoin\
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1269 -    Armory home dir       : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs    : 
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1271 -    Total Available RAM   : 4.00 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1272 -    CPU ID string         : Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1273 -    Number of CPU cores   : 2 cores
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1274 -    System is 64-bit      : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1275 -    Preferred Encoding    : cp1252
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1276 -    Machine Arch          : amd64
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1277 -    Available HDD (ARM)   : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1278 -    Available HDD (BTC)   : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1279 - 
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     thread_count    : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rescan          : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     ignoreAllZC     : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rescanBalance   : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     disableModules  : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     port            : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     interport       : 8223
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     coverageOutputDir: None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     forceWalletCheck: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     regtest         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rebuild         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     nettimeout      : 2
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     datadir         : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     clearMempool    : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     offline         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     armoryDBDir     : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_port   : 9001
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiPort     : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     useTorSettings  : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     netlog          : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     keypool         : 100
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     coverageInclude : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     forceOnline     : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     redownload      : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rpcBindAddr     : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     armorydb_ip     : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     multisigFile    : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     ram_usage       : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     mtdebug         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     logDisable      : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     settingsPath    : C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     language        : en
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     db_type         : DB_FULL
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     doDebug         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     enableDetSign   : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     disableConfPermis: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     testnet         : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     rpcport         : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiHome     : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     satoshiRpcport  : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     logFile         : C:\Bitcoin DBs\Armory DB\ArmoryQt.exe.log.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 -     verbosity       : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language  specified. Defaulting to English (en)
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-09 13:19 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-09 13:19 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.  
2017-05-09 13:19 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-09 13:19 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for 
2017-05-09 13:19 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2172 -    Wallet (xxx):    "Primary Wallet                  "   (Encrypted)
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user.  Done!
2017-05-09 13:19 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1682 -    From: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1690 -      To: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files (x86)\Armory
2017-05-09 13:19 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-09 13:19 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Bitcoin DBs\\Bitcoin Core']
2017-05-09 13:19 (INFO) -- SDM.pyc:443 - PID of bitcoind: 3152
2017-05-09 13:19 (INFO) -- SDM.pyc:444 - PID of armory:   4488
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '4488', '3152']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Bitcoin DBs\Bitcoin Core\blocks" --datadir="C:\Bitcoin DBs\Armory DB" --dbdir="C:\Bitcoin DBs\Armory DB\databases"
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Bitcoin DBs\\Bitcoin Core\\blocks"', u'--datadir="C:\\Bitcoin DBs\\Armory DB"', u'--dbdir="C:\\Bitcoin DBs\\Armory DB\\databases"']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode

Cheers.

[cryptoknut]

Can you use pruning in the new version of armory?