Armory 0.93 testing release! (with 0.05 BTC bug bounty)

[hardhouseinc]

Using Win7 64bit.
Yes, I used the downloader, that just gets the updated .exe
You have to do the install manually.

[1714619147]

1714619147

[1714619147]

1714619147

[1714619147]

1714619147

[Carlton Banks]

Since version 92.99.6, I've been getting these compile errors/warnings...

The first batch of warnings is because LMDBException inherits runtime_error so the catch is redundant, nothing too bad

The second set of warnings is just SWIG, nothing to see here really.

Was expecting you'd say something like that. If it doesn't bother the team, then it doesn't bother me.

I'm happily using 0.93, seems like a genuine milestone (I no longer have to plan ahead when I use Armory, as it definitely won't take 5 whole minutes to shut down!  )

[TimS]

0.92.99.7 supernode, Windows 7
I had two new transactions today, one sending and then one receiving. Both showed up when they had 0-conf, and then disappeared later, making Armory show an incorrect balance. I think each disappeared when it got a confirmation. Upgraded to 0.93, ran Help > Clear All Unconfirmed, and restarted Armory several times with no change.
Something that might have had an impact on this was that I also had a wallet loaded into Armory with ~131,000 imported private keys and many transactions on those addresses.

Wallet size will not impact supernode at all. This is some sort of scanning corner case. Can you see these transaction as part of the main chain in bc.info? I won't be going directly after this since I'm currently modifying a bunch of stuff in supernode for more stability and speed (this is for 0.93.1)

Yes, the transactions appear in the main chain, and no orphaned/other blocks (that bc.info is aware of).

[jammers]

Here are the bounty awards:

jammers - 5
TimS - 15
Helgabutters - 27
zombieslayer9099 - 4
japerry - 1
Bitpeep - 1
oneoctet - 1
Carlton Banks - 1
jouke - 2
justusranvier - 1
STRML - 1

Jammers, TimS and Helgabutters each received 2 bounties for all of their text formatting reports that were caused by internationalization.

Zombieslayer won 2 bounties for best suggestion for the paging control.

Please send me a PM if you think you are owed more bounties than you received.

So far only one of the above people has sent me the information that we need to pay you your bounties. PM that info to me if you are on this list and wish to be paid.

whohoo, 3rd glad to help guys!

[hardhouseinc]

Anyone have a similiar problem as this???

Just upgraded to new version 0.93
Did the full rebuild database option when it said it saw an old database version.

Now I get an unrepairable error.

Evey time I start-up Armory it completes building databases step
and appears to be 100% complete at the building portion.  Then it starts scanning
transaction history.  It appears to reach about 25% or less scanning
and gives an error it was interrupted, says you need to rebuild and
rescan at next startup.



https://www.dropbox.com/s/28onearkha0tuje/Screenshot%202015-02-22%2016.58.41.png?dl=0

Every attempt repeats the same error at the same  scanning percentage.
Have tried 100 different ways and still will not work properly.

[goatpig]

redownload the blockchain

[zombieslayer9099]

I have a question based on the new DB size, when using supernode will the DB still be as large as it is now?

[hardhouseinc]

redownload the blockchain

That was done on previous version to try and fix the problem but I had no luck.
Im trying to download now AGAIN, full factory reset, to see if that may work now on
the newest version.

[tpofo]

I got same problem of BDM error box.  It asks me to rebuild and rescan.  I did it twice and it loads once correctly, then after next time same error.
Anyone fix this?

[goatpig]

I have a question based on the new DB size, when using supernode will the DB still be as large as it is now?

No supernode is huge, ~90GB currently.

I got same problem of BDM error box.  It asks me to rebuild and rescan.  I did it twice and it loads once correctly, then after next time same error.
Anyone fix this?

That was done on previous version to try and fix the problem but I had no luck.
Im trying to download now AGAIN, full factory reset, to see if that may work now on
the newest version.

Open a support ticket, attach log files.

[solitude]

I got same problem of BDM error box.  It asks me to rebuild and rescan.  I did it twice and it loads once correctly, then after next time same error.
Anyone fix this?

I'm getting the same BDM error.  I've already uninstalled both Bitcoin Core and Armory twice now, redownloaded the entire blockchain maybe three or four times, nothing works.

I made a post in the "official" 0.93 thread along with others having the issue.

I can't believe 0.93 went live with this huge bug affecting so many people. 

[solitude]

Open a support ticket, attach log files.

I've done this also. 

It says an email will be sent to my email telling me how to create an account, to check my ticket status.

I haven't received any email, and it's been about 20 hours.

I'd rather not create an account, I'd just like a reply to the email I supplied.

[goatpig]

I need your log files, one way or another (both armorylog.txt and armorycpplog.txt)

Either go through the support channel or post them somewhere and give me the link.

[Searinox]

Got btc core 0.10 and armory 0.93. After a lot of freezing up and a failed database read, and rebuilds of armory's database that kept freezing up, I deleted everything in my btc core and armory folder, so everything blockchain-related from both btc core and armory's own database is gone, the only things I kept were ArmorySettings.txt and my Armory wallet. I was hoping that a fresh re-download of the blockchain and rebuild from scratch would fix stuff. Instead armory is now freezing up at 0% synchronizing with network. The little spinning disk animation is frozen but the UI is still responsive. There is no disk activity. I'm at a loss here. I'm attaching the logs from btc core and armory's two logs here in hopes someone can figure out what is going on. I have been using armory fine for a year now.

https://www.dropbox.com/s/8l9yh5vvp358apn/searinox-inactive_armory.zip?dl=0

[goatpig]

Got btc core 0.10 and armory 0.93. After a lot of freezing up and a failed database read, and rebuilds of armory's database that kept freezing up, I deleted everything in my btc core and armory folder, so everything blockchain-related from both btc core and armory's own database is gone, the only things I kept were ArmorySettings.txt and my Armory wallet. I was hoping that a fresh re-download of the blockchain and rebuild from scratch would fix stuff. Instead armory is now freezing up at 0% synchronizing with network. The little spinning disk animation is frozen but the UI is still responsive. There is no disk activity. I'm at a loss here. I'm attaching the logs from btc core and armory's two logs here in hopes someone can figure out what is going on. I have been using armory fine for a year now.

https://www.dropbox.com/s/8l9yh5vvp358apn/searinox-inactive_armory.zip?dl=0

I'm not sure if you are trying to get the torrent bootstrap going or if you already have Core sync'ed with a fresh blockchain. The log says bitcoind started but it's not reporting a blockchain folder size which would purport you have a fresh Core datadir. At this point it's getting confusing.

One thing I'm noticing that you should really avoid is: "--datadir=E:\Program Files (x86)\Armory\Data_Armory"

Program Files(x86) is a binary folder. In that regard, a process would need admin privileges to write files in there, and chances are you aren't (neither do you want) to run Armory as admin. This alone will trip Armory. You should use a folder for which your current user has privileges, usually somewhere in the C:\user\*username* folder, or another drive/non system partition.

If this doesn't fix it, then you should bypass bitcoind automanagement. Start BitcoinQt manually and get it to sync the full chain. If you want to speed that process up you can get the bootstrap torrent on your own and move the fully downloaded bootstrap into your Core datadir folder.

With that done, start Armory and report on what happens. Ideally you should do that in a support ticket.

[Roy Badami]

I'm assuming I shouldn't be seeing the "Armory is incompatible with Bitcoin Core 0.10+" message in the announcements tab of the dashboard - given that I'm running 0.93 release :-)

It's under the heading "All available notifications" - not sure if that's supposed to mean that it includes notifications that don't apply to me (but if this really is the intended behaviour then may I respectfully suggest that you reconsider your UI design here)

roy

[goatpig]

I'm assuming I shouldn't be seeing the "Armory is incompatible with Bitcoin Core 0.10+" message in the announcements tab of the dashboard - given that I'm running 0.93 release :-)

It's under the heading "All available notifications" - not sure if that's supposed to mean that it includes notifications that don't apply to me (but if this really is the intended behaviour then may I respectfully suggest that you reconsider your UI design here)

roy

The annoucement/downloader is kind of all over the place right now, sorry about that. I think what you are getting a version agnostic warning about Core 0.10 when it was only meant to hit 0.92.3 and earlier. We'll get it under control eventually.

[zombieslayer9099]

I don't know if this has already been brought to developers' attention, but here:

When signing a tx (from simulfunding, or any unsigned tx really), occasionally it fails and returns this lovely message in the log:

Code:

2015-02-24 15:27 (ERROR) -- Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/MultiSigDialogs.py", line 2716, in doSign
    self.doSignForInput(idstring, nIdx)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/MultiSigDialogs.py", line 2936, in doSignForInput
    ustxi.createAndInsertSignature(pytx, addrObj.binPrivKey32_Plain)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 1275, in createAndInsertSignature
    derSig = self.createTxSignature(pytx, sbdPrivKey, hashcode, DetSign)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 1235, in createTxSignature
    raise SignatureError('No PubKey that matches this privKey')
SignatureError: No PubKey that matches this privKey

This doesn't happen often but I thought I'd report it anyway

[goatpig]

I don't know if this has already been brought to developers' attention, but here:

When signing a tx (from simulfunding, or any unsigned tx really), occasionally it fails and returns this lovely message in the log:

Code:

2015-02-24 15:27 (ERROR) -- Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/MultiSigDialogs.py", line 2716, in doSign
    self.doSignForInput(idstring, nIdx)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/MultiSigDialogs.py", line 2936, in doSignForInput
    ustxi.createAndInsertSignature(pytx, addrObj.binPrivKey32_Plain)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 1275, in createAndInsertSignature
    derSig = self.createTxSignature(pytx, sbdPrivKey, hashcode, DetSign)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 1235, in createTxSignature
    raise SignatureError('No PubKey that matches this privKey')
SignatureError: No PubKey that matches this privKey

This doesn't happen often but I thought I'd report it anyway

We're aware of this one. Didn't work a fix for 0.93 but will most likely have one for .1

[Searinox]

Got btc core 0.10 and armory 0.93. After a lot of freezing up and a failed database read, and rebuilds of armory's database that kept freezing up, I deleted everything in my btc core and armory folder, so everything blockchain-related from both btc core and armory's own database is gone, the only things I kept were ArmorySettings.txt and my Armory wallet. I was hoping that a fresh re-download of the blockchain and rebuild from scratch would fix stuff. Instead armory is now freezing up at 0% synchronizing with network. The little spinning disk animation is frozen but the UI is still responsive. There is no disk activity. I'm at a loss here. I'm attaching the logs from btc core and armory's two logs here in hopes someone can figure out what is going on. I have been using armory fine for a year now.

https://www.dropbox.com/s/8l9yh5vvp358apn/searinox-inactive_armory.zip?dl=0

I'm not sure if you are trying to get the torrent bootstrap going or if you already have Core sync'ed with a fresh blockchain. The log says bitcoind started but it's not reporting a blockchain folder size which would purport you have a fresh Core datadir. At this point it's getting confusing.

One thing I'm noticing that you should really avoid is: "--datadir=E:\Program Files (x86)\Armory\Data_Armory"

Program Files(x86) is a binary folder. In that regard, a process would need admin privileges to write files in there, and chances are you aren't (neither do you want) to run Armory as admin. This alone will trip Armory. You should use a folder for which your current user has privileges, usually somewhere in the C:\user\*username* folder, or another drive/non system partition.

If this doesn't fix it, then you should bypass bitcoind automanagement. Start BitcoinQt manually and get it to sync the full chain. If you want to speed that process up you can get the bootstrap torrent on your own and move the fully downloaded bootstrap into your Core datadir folder.

With that done, start Armory and report on what happens. Ideally you should do that in a support ticket.

I've not been using the torrent ever. Everything is running with admin privs as UAC has been disabled from day 1 of windows install(5.5 years ago) and there is only one admin account on the pc.

I have an update. Apparently bitcoin WAS actually downloading the blockchain, but the UI updates like only once every 12 hours or so! The size of the Data_BTC folder steadily increased to 34GB then it began building the Armory DB. Again, the UI did NOT update, with the spinning disk animation perfectly still... at around 16GB it updated ONCE, and is now showing "Building Databases 61.5%", it has since reached 18.9GB(of what was previously ~29GB) and then STOPPED growing in size. There is intense activity but the size is not growing anymore, not even by a handful of bytes.

On a separate laptop machine, Armory's UI is doing the same, it has downloaded 32/34GB blockchain but the UI still stood at 0% from late last night until only early this moment when it jumped to 95% and is again frozen despite the chain still being downloaded.

So at this point I am unsure what Armory's DB is doing as it has stopped growing in size even though there's still constant disk activity, all I know is that the UI, which updates extremely rarely, is making my confusion worse.