Creating wallet ... forever?

[lordbah]

Built Armory from source, on Ubuntu 13.10 64-bit, started it up, told it to create a wallet. "Please wait ... Creating wallet ..." with two progress bars hidden behind it. In a few minutes the first progress bar completed (bitcoind was already up-to-date). After a longer time the second progress bar completed, whatever it was (should probably move that dialog so we can see the progress bars). For the past 8 hours apparently nothing has been happening - no heavy CPU usage, nothing much happening on the network or hard disk (python is using 625 MB memory). But that "Please wait ... Creating wallet ..." dialog is still there. Can it really take 24 hours to create your first wallet even when bitcoind already has the whole blockchain? Occasionally stdout says "Added new blocks to memory pool: 1" but no errors. I guess it's still not finished because nothing has appeared underneath "Available wallets". It would be good to have some visual reassurance that it isn't just plain dead, that some progress is being made - if in fact it is.

[goatpig]

Some Python side crash halted everything. Do you have a wallet loaded and was the consistency check running before when the progress bar hit 100%? Progress bars come with a label, what did the bars say. It's surprising that you have 2 of these running. Try to create your wallet offline and see if that completes.

Btw, which branch did you build from?

[lordbah]

Erm ... as for what branch, I did what the instructions said

git clone git://github.com/etotheipi/BitcoinArmory.git

Hopefully something in that answers your "which branch" question.

I did not have a wallet loaded, I was creating my first Armory wallet, which it prompted me to do as soon as I launched it. My intention was that I would create a new address and send my existing bitcoins to it, rather than importing my existing wallet.

The progress bar labels were obscured by this "Please wait ... Creating wallet ..." dialog. My impression was that the top one was for the blockchain, although I can't remember specifically why I thought that.

It's still at the same place 22 hours later. I will kill it and restart.

--

Okay, after restarting, it lists one wallet, and the two progress bars are "Initializing Bitcoin Engine" which later morphs into "Synchronizing with Network" and is 100% before I finished writing this, and "Scanning Transaction History" which should complete in 10 minutes.

Is there any way to figure out and report what crashed the first time?

[lordbah]

Made a paper backup and tested it when invited to do so. "Bad Backup!". I've triple-checked that I entered all the letters correctly. Guess I might as well delete this wallet and create a new one - I haven't used it yet. The "new user experience" has been less than ideal.

[goatpig]

Made a paper backup and tested it when invited to do so. "Bad Backup!". I've triple-checked that I entered all the letters correctly. Guess I might as well delete this wallet and create a new one - I haven't used it yet. The "new user experience" has been less than ideal.

Bad backup means the internal error checking on the backup is erroneous. That's some deep data corruption. I have never ran into this. You should make a new wallet indeed, and make sure to test your backup before sending funds to the wallet.

You pulled the master branch. You should be pulling the testing branch right now. Browse to the Armory source folder and do this:

git fetch
git checkout testing
make clean
make

[lordbah]

Done. Thanks.