I cleared out all wallets from my past installation of armory and placed only my current wallet in the directory. Another wallet appears in the directory and is never logged into the Armory wallet list in the GUI. Is there a reason why there is another "invisible" wallet appearing in the armory directory? Does Armory use any wallet resources other than the ones created by the user?
Is it safe to delete all the wallets that are not listed in the wallet list in GUI?
Update: Oops, I answered my own question. I deleted them and then I was presented with a popup message upon launching Armory. The popup happens quick so I never noticed upon installation of Armory 0.96. They are watch only wallets and mirror the original wallets, which contain the private keys.
Update 2: I was conducting a test of a restore of my paper wallet. The wallet was correctly imported and wallet string matched. However, Armory crashed with following error:
dbLog.txt:
Log file opened at 1499973596: e:\Armory/dbLog.txt
-INFO - 1499973596: (..\main.cpp:23) Running on 8 threads
-INFO - 1499973596: (..\main.cpp:24) Ram usage level: 4
-INFO - 1499973596: (..\BlockUtils.cpp:907) blkfile dir: E:\Bitcoin\blocks
-INFO - 1499973596: (..\BlockUtils.cpp:908) lmdb dir: e:\Armory\databases
-INFO - 1499973596: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1499973598: (..\BDM_Server.cpp:996) registered bdv: 7519440fd3d3f120b88f
-INFO - 1499973600: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1499973600: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1499973604: (..\DatabaseBuilder.cpp:208) Found 475688 headers in db
-INFO - 1499973607: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1499973607: (..\DatabaseBuilder.cpp:477) Found next block after skipping 351001bytes
-INFO - 1499973608: (..\DatabaseBuilder.cpp:268) parsed block file #933
-DEBUG - 1499973608: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1499973608: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.696s
-INFO - 1499973608: (..\DatabaseBuilder.cpp:106) scanning new blocks from #475688 to #475687
-INFO - 1499973608: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1499973608: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1499973608: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.01s
-INFO - 1499973608: (..\DatabaseBuilder.cpp:160) init db in 8.161s
-INFO - 1499973608: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1499973608: (..\BDM_supportClasses.cpp:366) Starting address registration process
--ERROR - 1499973608: (..\BlockchainScanner.cpp:ERROR - 1499973608: (..\BlockchainScanner.cpp:-ERROR - 1499973608: (..\BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 1499973608: (..\BlockchainScanner.cpp:
I then went to delete the mirror wallets so Armory can regenerate them. Still same error.
So, there seems to be an issue when I restore wallet from paper. I place back the original .wallet file and also remove mirror wallets. Armory works ok after this. It does not seem to like the restored wallet for some reason.