You possibly installed BitcoinQt in a non default folder, in which case you have to point armory to the blockchain folder with the --satoshi-dir command line argument

I'm not 100% positive about this but I don't think Armory depends on the incriminated packages.

Armory 0.90 for Windows was built against Python 2.7.5. We will update to 2.7.6 for 0.91

https://github.com/etotheipi/BitcoinArmory/blob/0.91-dev/armoryengine/ArmoryUtils.py#L45

You can see all the current active (and unactive) command line args here, with their associated help comments.

This branch is being pushed to daily. We're not gonna release signed packages daily, sorry.

Like any other software out there, you get a triangle: core innovation, update frequency, stability. If you want to sit on the passive end user side, you only get to enjoy 2 out of 3, and that's the 2 the dev team picks.

As I've said elsewhere, I have identified the bug causing your crash, which is somehow limited to your use case only. Remember this is an open source software, that it comes to you at no cost, and that it is still in beta.

If you want the latest updates and fixes but dont want to wait for releases, feel free to clone the current branch marked as -dev from our github repo and build away. The build process is very simple on Debian/Ubnutu, and not all that hard on Windows. You could also try and help us isolate your particular bug.

Your case seems rather limited, you are about the only user I have heard off that has Armory entirely crash on sends. I remember getting a log file from you and finding the particular error. I fixed that but I still do not understand what you are doing that it somehow only affects you and not all of our users.

As for 0.91, this is still being deved, although it has the fix for your particular case (at least from what I could identify from your log file). Feel free to checkout the 0.91-dev branch, it's quite easy to do on Debian/Ubuntu.

That's in the 0.91-dev branch on github. Still a few weeks until we release this officially. The team is in the process of fixing the known comon bugs in this branch.

Are you using an older version of Armory that you create offline transactions from? The rescan on crash is fixed for 0.91

Sounds like a corrupt DB, clean that up and restart (delete the database folder in Armory's datadir)

As someone once told me:

- short answer: yes
- long answer: yes

This is pretty weird, it looks like it is catching non bitcoin: URIs for some reason. Gotta investigate.

Not any time soon, but possibly

As long as your paper backup only carries a root key, that all you need

We dont currently support unicode characters in the wallet files (where the comments on txn are saved) so these are currently turned off. We plan on having full unicode support for the new wallet format.

As for the other errors:

The BDM closing thing is not an error, it simply is broadcasted through LOGERROR() which starts the line with an (ERROR) tag.

The other errors relate to old code that kinda go left alone and now needs some fixing, but is in no way fatal.

Well you're still looking at a 256bit integer collision, that's the same as hoping for a private key collision.

I mistunderstood the topic here, I thought Carlton was looking for online capacity. Granted we have a inhouse Raspbian build for Armory now, it wouldn't be too hard to get it online on a Pi, assuming you sync BitcoinQt and build Armory's DB on another machine, but I would recommend against it regardless =P.

To clear all misunderstandings, I use my Pi as my offline Armory signer.

In this case you can expect any of the .deb offline bundles to work with any Tails.

Raspbian for online Armory? Ouch! Already takes me like 2 minutes to sign a single transaction with 1 output and change 0.0

try bind=localhost in bitcoin.conf

Interesting, it works for me without using Tor. Try bind=localhost, maybe your host file resolves localhost to something else (IPv6?)