Armory - Discussion Thread

[etotheipi]

F*ck, after restart and started Armory again i see now sign transaction dialog.
I don't understand this beta version...
It's very buggy. Some dialogs work same: click -> nothing -> click -> ok -> click -> nothing -> click -> nothing -> click -> OK -> click -> OK
It remains me a mining

Please send us your log file.  Do so within the app (Help->Submit Bug Report).  It will automatically include the log file when you do. 

When you click a button and it doesn't do anything, it's usually a very simple bug that we can fix but only if we see the log file.

[Perlover]

Please send us your log file. 

Done!

[doug_armory]

Hey everyone. I have some good news and bad news. The good news is that 0.92 has been released! The bad news is that the OS X build is borked. I'm looking into it and think I know what happened. In the meantime, hang tight. We'll get a corrected build out ASAP. (As far as I know, the Linux and Windows builds are fine.)

Sorry about the botched launch. I'll look into solutions to ensure that this doesn't happen again. In the meantime, I just confirmed that the 0.91.99.11 build works. You can download it from here if you can't wait. It's 0.92 minus a few very small, last-minute changes.

[plethora]

Hey, I've just upgraded from 0.91.2 to 0.92. All my wallets are listed normally but the Transactions list are missing transactions and Maximum and Spendable funds just displays about 30% of my funds. I've tried restarting Armory and Rescan Databases but it didn't help.

Do you think Rebuild and Rescan Databases could help?
Do I need to reimport the wallets?
How else can I troubleshoot this issue?

Thanks

[CircusPeanut]

Hey, I've just upgraded from 0.91.2 to 0.92. All my wallets are listed normally but the Transactions list are missing transactions and Maximum and Spendable funds just displays about 30% of my funds. I've tried restarting Armory and Rescan Databases but it didn't help.

Do you think Rebuild and Rescan Databases could help?
Do I need to reimport the wallets?
How else can I troubleshoot this issue?

Thanks

It's hard to tell what your problem without seeing the logs. As stated by Etotheipi you can send us the log file from within Armory (Help->Submit Bug Report). 

Look at the top block number displayed in the lower right corner of Armory. If it matches the number in blockchaininfo there should be no need to rebuild/rescan the databases.

I don't think reimporting the wallets should make a difference, but it can't hurt. Note that you can reimport a wallet without deleting it. It is never necessary to delete a wallet.

[cypherdoc]

Hey everyone. I have some good news and bad news. The good news is that 0.92 has been released! The bad news is that the OS X build is borked. I'm looking into it and think I know what happened. In the meantime, hang tight. We'll get a corrected build out ASAP. (As far as I know, the Linux and Windows builds are fine.)

Sorry about the botched launch. I'll look into solutions to ensure that this doesn't happen again. In the meantime, I just confirmed that the 0.91.99.11 build works. You can download it from here if you can't wait. It's 0.92 minus a few very small, last-minute changes.

would this include Ubuntu versions installed within a VM on a Mac?

[goatpig]

Hey everyone. I have some good news and bad news. The good news is that 0.92 has been released! The bad news is that the OS X build is borked. I'm looking into it and think I know what happened. In the meantime, hang tight. We'll get a corrected build out ASAP. (As far as I know, the Linux and Windows builds are fine.)

Sorry about the botched launch. I'll look into solutions to ensure that this doesn't happen again. In the meantime, I just confirmed that the 0.91.99.11 build works. You can download it from here if you can't wait. It's 0.92 minus a few very small, last-minute changes.

would this include Ubuntu versions installed within a VM on a Mac?

You shouldn't be concerned

[goatpig]

Hey, I've just upgraded from 0.91.2 to 0.92. All my wallets are listed normally but the Transactions list are missing transactions and Maximum and Spendable funds just displays about 30% of my funds. I've tried restarting Armory and Rescan Databases but it didn't help.

Do you think Rebuild and Rescan Databases could help?
Do I need to reimport the wallets?
How else can I troubleshoot this issue?

Thanks

Make a ticket, add your log. Verify in the bottom left corner drop down list that "all wallets" is selected.

[plethora]

I don't think reimporting the wallets should make a difference, but it can't hurt. Note that you can reimport a wallet without deleting it. It is never necessary to delete a wallet.

I wasn't able to reimport import the wallet. Armory says that there's already a wallet with the same ID loaded and that I first need to remove it before importing it again. Once I did that I was returned to the Restore Wallet window which I had to Cancel and now it just keeps reloading all other wallets (I can see all other .watchonly.wallet files being constantly rewritten in a loop). I'll make a ticket including logs.

[cypherdoc]

Hey everyone. I have some good news and bad news. The good news is that 0.92 has been released! The bad news is that the OS X build is borked. I'm looking into it and think I know what happened. In the meantime, hang tight. We'll get a corrected build out ASAP. (As far as I know, the Linux and Windows builds are fine.)

Sorry about the botched launch. I'll look into solutions to ensure that this doesn't happen again. In the meantime, I just confirmed that the 0.91.99.11 build works. You can download it from here if you can't wait. It's 0.92 minus a few very small, last-minute changes.

would this include Ubuntu versions installed within a VM on a Mac?

You shouldn't be concerned

in a typical installation, should the Bitcoin Install directory be in the .armory folder and the Bitcoin Home Directory be in the home directory?

[doug_armory]

Hey everyone. I have some good news and bad news. The good news is that 0.92 has been released! The bad news is that the OS X build is borked. I'm looking into it and think I know what happened. In the meantime, hang tight. We'll get a corrected build out ASAP. (As far as I know, the Linux and Windows builds are fine.)

Sorry about the botched launch. I'll look into solutions to ensure that this doesn't happen again. In the meantime, I just confirmed that the 0.91.99.11 build works. You can download it from here if you can't wait. It's 0.92 minus a few very small, last-minute changes.

would this include Ubuntu versions installed within a VM on a Mac?

No. That should be totally fine.

If anyone's curious, the OS X issue has to do with how we build Armory. It uses a totally separate process than Linux and Windows. It usually works fine. It does occasionally fail, unfortunately. I'm looking into ways to make this a thing of the past. Unfortunately, the only surefire way would require us to add ~300 MB worth of data to the repo. I'll see if I can figure out an alternative that Alan and others can use when building. In fact, sitting here just now, I think I figured out a solution. If I choose to implement it, the solution should make build failures like this a thing of the past.

Speaking of OS X, I have some good news for everybody. Last night, I finished some code that brings notifications back to OS X, at least if you're running 10.8 or higher. The code will also change the dock icon to green when in testnet mode, like BC Core does (along with the Linux and Windows versions of Armory). I don't know when the code will be merged in but it should be relatively soon. It may also need a bit of tweaking over the coming weeks but it seems reasonably solid at the moment.

The best part is that this delivery will build a permanent bridge between Armory and the Objective-C language, which you must use to access certain OS X features. If Armory adds features that require Objective-C on OS X, feature parity should be achieved eventually. (Obviously, I won't promise anything right now. Every feature has its own set of requirements.)

[plethora]

Verify in the bottom left corner drop down list that "all wallets" is selected.

haha this is embarrassing 
I've never seen that drop down before. It was set to My Wallets but didn't display all my wallets anyway. However after changing to All Wallets and then back to My Wallets again all is fine 

I'll try to import a wallet once more to see if I'll get that other issue again.
Thanks!

[CircusPeanut]

I don't think reimporting the wallets should make a difference, but it can't hurt. Note that you can reimport a wallet without deleting it. It is never necessary to delete a wallet.

I wasn't able to reimport import the wallet. Armory says that there's already a wallet with the same ID loaded and that I first need to remove it before importing it again. Once I did that I was returned to the Restore Wallet window which I had to Cancel and now it just keeps reloading all other wallets (I can see all other .watchonly.wallet files being constantly rewritten in a loop). I'll make a ticket including logs.

Are you sure that you are running 0.92? Only older versions of Armory ask you to remove the wallet with the same ID before restoring it.

[plethora]

Yes, I downloaded and installed 0.92 using Armory's Secure Downloader.

[CircusPeanut]

Yes, I downloaded and installed 0.92 using Armory's Secure Downloader.

Hmm, we must be restoring differently...



How are you restoring the wallet?

EDIT: I see now that you must have been restoring a digital backup. I think we need to make sure that Armory gives the same response regardless of how a wallet is restored.

[plethora]

Ah, I'm using "Import digital backup or watching-only wallet".

[justusranvier]

What would cause Armory to fail to recognize that new blocks have arrived?

In this case, bitcoind is running on a separate machine, with NFS used to share the blockchain directory and socat used to tunnel Armory's connection requests to 127.0.0.1:8333 to the appropriate interface.

Indexing the blockchain works just fine, sending transactions works just fine, and Armory does notice incoming unconfirmed transactions.

However the block count in the lower-right corner never increment, requiring a restart in order to notice that new blocks have arrived.

[etotheipi]

What would cause Armory to fail to recognize that new blocks have arrived?

In this case, bitcoind is running on a separate machine, with NFS used to share the blockchain directory and socat used to tunnel Armory's connection requests to 127.0.0.1:8333 to the appropriate interface.

Indexing the blockchain works just fine, sending transactions works just fine, and Armory does notice incoming unconfirmed transactions.

However the block count in the lower-right corner never increment, requiring a restart in order to notice that new blocks have arrived.

It sounds like it's finding the block files fine on startup, but sees them staying the same size after that..  Armory reads new blocks by observing the last block file changing size or the creation of a new blk file.  Perhaps NFS is not allowing up to date access to that info.

[cypherdoc]

where do i paste ".bitcoin" and it's full blockchain so that Armory will find it during a new installation?  Ubuntu within a VM on a mac os. IOW, where is the default location where Armory looks to find this?

[doug_armory]

where do i paste ".bitcoin" and it's full blockchain so that Armory will find it during a new installation?  Ubuntu within a VM on a mac os. IOW, where is the default location where Armory looks to find this?

All info is here. In the particular case of Linux, /home/<username>/.bitcoin is where Armory looks by default.