I am having problems running after upgrade to Mint 20.04.  Mint 20.04 is based on Ubuntu 20.04 LTS (Focal Fossa).
I tried to reinstall and some dependencies fail.
On execution I get:

Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 36, in <module>
    from PyQt4.QtCore import *
ImportError: No module named PyQt4.QtCore


On trying to reinstall from archive, I get:

dpkg: dependency problems prevent configuration of armory:
 armory depends on python-qt4; however:
  Package python-qt4 is not installed.
 armory depends on python-psutil; however:
  Package python-psutil is not installed.

I tried to install python-qt4 and other dependencies, but had some issues as well. 

Anyone get armory working on the new Mint or Ubuntu?

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:  

Code:

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.

I just thought it would be great to maybe have the option to supply the private key to armory for seeding armory wallet.  It would be nice to generate a new wallet outside of armory.
Say, roll dice / use cards to make a private key if one is not confident with csprng.  Armory would take this private key and use it as a seed for the deterministic wallet.

I understand there is a manual entropy feature when generating a wallet in Armory.  Is this equivalent in true randomness(not pseudo random like all computer rng are) when used?

Any thoughts on this feature?

I am not sure if other people are getting this issue.  I have read on here and it doesn't seem exactly posted as I am experiencing it.
I have to say I love Armory Bitcoin wallet.  There is no other wallet out there that comes close.  It has all the features I want and the trust and security I want.
So, I use it no matter if it is buggy sometimes because I still trust it.  I found the older versions were more rock solid in terms of giving current balances and transactions.  But, the newer version works much much faster with its own database.  The old one took about the same as the bitcoin core.  The new one is very small.  SO that is a major plus.

The problem I have is that sometimes(it happens randomly) it does not give me current balance although I verified it has downloaded all blocks and is current.  I tried it 2 ways.  I sync it with core first, then load Armory.  I also try just letting Armory do it with bitcoind.  Both ways sometimes(maybe 1 out of 10 times or so) will not give me current balance.

I get this from the console and it halts with no other lines.

Code:

-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads

The way I can get around this issue is to only rescan and rebuild armory database.  Then, I have current balance.  Why is my armory not 100% robust and flawless in scanning database when I load it?

I already submitted a support ticket.  I am just posting a brief description here in case anyone else may have had the problem.
I upgraded bitcoin core to 0.11.1, ran it, waited for total sync.
I upgraded Armory to 0.93.3, ran it, and waited for total sync.

I did not see my most recent transaction(receiving).  So, I verified in blockchain, and it is verified. 
Then, I exported key to bitcoin core and my transaction was there, no problem.  However, Armory does not see it.  I already tried rebuilding and rescanning database.

Anyone ever had this?

I've been having some fun playing around with Armory code and using the API.  I would like to scan the blockchain and probe it for different statistics of interest.
Mainly, for now, I would like to generate BTC address lists of top balances, etc...  Is there an easy builtin function to do this?  I don't mind if it is with python frontend code or the CPP backend code.  Whichever is easiest and most straightforward.

Thanks in advance for any help.

I tried to submit the bug through Armory and it gave error.  I went to website and there is no active link under Support.  I am submitting a bug report here.

I get the following error when it syncs at the beginning.  
I have the latest bitcoin and armory client.
I tried rebuilding and restarting.  It worked once.  Then back to same error.

BlockDataManager Warning

DB failed to open, reporting the following error: Failed to open dbi (MDB_INCOMPATIBLE:  Operation and DB, or DB flags changed)


I looked inside log and the only error I see is:  2015-06-22 02:09 (ERROR) -- announcefetch.pyc:312 - Could not verify data in signed message block

UPDATE:  I did a rebuild and scan again.  It seems to have worked for a couple of times now.  So, no problem for now. Problem solved.
It would have been nice to know what happened in case it happens again.  So far, it was twice it happened.

First off, I think Armory is the best wallet. It is the only wallet I use.

Recently, I have been playing around with the python scripting in Armory.  I managed to successfully build Armory from source on windows using VS2013.  I ran Armory from python.  Everything works correctly.

I built Armory exactly with the versions of 32bit tools that were defined by the compiling in windows doc.  I used exact versions of everything.
I am using swigwin2.04 as well.  Compiling and post build process succeeded in 4 successful projects.

Now, when I try running some of the examples you included: 
Specifically testswig.py, examples in extras, and examples in pytest, I get some weird errors.
Some examples run perfectly, however, ones that I want to test like scanning the blockchain for a certain address/wallet fail.

I usually get:

Traceback (most recent call last):
  File "C:\API\Projects\BitcoinArmory\extras\sample_armory_code.py", line 29, in <module>
    cppWallet.addAddress_1_( hex_to_binary('11b366edfc0a8b66feebae5c2e25a7b6a5d1cf31') )  # hash160 (hex)
  File "..\CppBlockUtils.py", line 1690, in <lambda>
    __getattr__ = lambda self, name: _swig_getattr(self, BtcWallet, name)
  File "..\CppBlockUtils.py", line 53, in _swig_getattr
    raise AttributeError(name)
AttributeError: addAddress_1_

OR

(ERROR) Traceback (most recent call last):
  File "C:\API\Projects\BitcoinArmory\extras\sample_armory_code.py", line 83, in <module>
    cppWallet.addAddress_1_( hex_to_binary('0cdcd0f388a31b11ff11b1d8d7a9f978b37bc7af') )
NameError: name 'cppWallet' is not defined

Traceback (most recent call last):
  File "C:\API\Projects\BitcoinArmory\extras\sample_armory_code.py", line 83, in <module>
    cppWallet.addAddress_1_( hex_to_binary('0cdcd0f388a31b11ff11b1d8d7a9f978b37bc7af') )
NameError: name 'cppWallet' is not defined

Basically, I would like a simple working script for scanning blockchain quickly for an address in my local armory blockchain dir.

As an aside, is it possible to use your API without python?  I enjoy using C++ more directly.  But, no matter, I am comfortable just the way you have the python scripting working if it is too much trouble to explain.

Thanks in advance.