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

[etotheipi]

Armory 0.93 Testing Release  (0.92.99.7-testing)
Bug Bounty Started:  0.05 BTC per bug!



REMEMBER:  Download links are at the bottom but you can get the new version through the secure downloader.  Armory will check the signatures for you!

NOTE:  If you upgrade Core to 0.10 you must use this new version of Armory.  Armory 0.92.3 and older does not work with headers-first!


Hi all,

Finally, we have a solid testing release for 0.93.  This version has taken us quite a long time because it represents a substantial reworking of the blockchain engine as well as the inter-thread communication.  Much of Armory looks the same as it did in previous versions, but now it's 100% scalable, handling wallets that even have a 1,000,000+ addresses and transactions in their history.  It also does things in the background such as address and wallet imports, which no longer force you offline.  Because of the new threading engine, there's a whole class of stability problems that don't exist anymore (specifically BDM timeout errors that cascaded into unusability and required restarting Armory;  usually with larger wallets).  

Special thanks to goatpig and njaard who have spent many months the new blockchain engine!

Especially important for our more-hardcore users, we now have a "supernode" mode, that doubles Armory's DB size, but indexes all scripts on the blockchain.  If you delete your databases and start Armory with "--supernode", you'll build a DB that does instant importing of addresses and wallets.  It could be used to build a block explorer or an Electrum-style server for feeding lite-nodes (for everyone who's asked about lite-Armory, completion of supernode was a critical milestone that needed to be crossed to even think about it).

KEEP IN MIND:  This new version uses a new DB engine (LMDB instead of LevelDB).  This means that the 0.93 databases are incompatible with any already-built databases.  And it won't delete them automatically -- you must do it manually if you don't want both versions.  This was done to accommodate users that have to jump back to 0.92 if the latest version doesn't work for them.  We recommend simply using a new datadir for testing.


REMEMBER:  You can always get the new version through the secure downloader.  Armory will check the signatures for you!  Download links are provided here as a convenience for those testing in non-secure environments.

NOTE2:  I have no expectations of the OSX build working.  If it does, it would be a blessing.  We've had to stir some things up, and didn't have time to solidify before this testing release.  It'll come soon!

  Armory 0.92.99.7-testing for Windows XP, Vista, 7, 8+ (32- and 64-bit)
  Armory 0.92.99.7-testing for MacOSX 10.7+ (64bit)
  Armory 0.92.99.7-testing for Ubuntu 12.04+ (32bit)
  Armory 0.92.99.7-testing for Ubuntu 12.04+ (64bit)
  Armory 0.92.99.7-testing for RaspberryPi  (armhf)

  Armory 0.92.99.7-testing Offline Bundle for Ubuntu 12.04 exact (32bit)
  Armory 0.92.99.7-testing Offline Bundle for Ubuntu 12.04 exact (64bit)
  Armory 0.92.99.7-testing Offline Bundle for RaspberryPi  (armhf)

  Armory 0.92.99.7-testing: Signed hashes of all installers




Semi-official changelog:


VERSION 0.92.99.7
Released Jan 9, 2015


   - New Scalable Blockchain Engine
        This version of Armory will look very similar to previous versions,
        but actually has a completely new, scalable database engine (using
        LMDB instead of LevelDB).  The engine can now handle wallets with
        millions of addresses and transactions!

   - Compatible with Bitcoin Core 0.10 and "headers-first"
        The most recent version of Bitcoin Core includes a parallel network
        synchronization feature called "headers-first" which is incompatible
        with previous versions of Armory.  This version is required to use
        with Bitcoin Core 0.10 and newer.  Torrent-based bootstrapping will
        be removed in the next version of Armory.

   - Improved Threading and Reliability
        With the new backend comes overhauled inter-thread messaging.  This
        resolves a ton of stubborn stability issues that Armory has had in
        the past, especially with large wallets and transaction histories.  

   - Address and Wallet Importing in Background
        Importing wallets and addresses now induces background scans which
        do not disable the interface (previously forced you into offline
        mode for the duration of the scan).  
        
   - Supernode Mode
        Use the "--supernode" flag before creating the databases to create
        a supernode database that enables instant address & wallet import.
        This is an enabling feature for high-volume, consumer facing apps
        and services to be built on Armory, such as exchanges and block-
        explorers.  NOTE: Running with --supernode will result in an Armory
        database approximately double the size of the blockchain!  
        
   - Improved armoryd.py
        The daemon version of armory, armoryd.py, has been fully updated and
        tested with the new database engine.  Also includes a new "webshop"
        sample application that demonstrates basic usage of armoryd.py to
        collect & verify payments, generate unsigned transactions, etc.

[1714038868]

1714038868

[1714038868]

1714038868

[1714038868]

1714038868

[1714038868]

1714038868

[1714038868]

1714038868

[doug_armory]

Hey everyone. As Alan said, the OS X version will probably still be a bit unstable for some people. The good news is that I have a significant fix in mind. An upgrade to Qt (an underlying library) is supposed to be released next month. I've been doing some testing with a "snapshot" version. It fixes several annoying problems I've seen and have been unable to fix. I thought about including it in this release but I wasn't sure if people would be comfortable using a snapshot build that wasn't from an official source. In any event, the LMDB DB seems stable on my machine. I've used it to conduct quite a few significant mainnet and testnet transactions. No problems occurred. As always, though, there may be some bugs I'm not aware of. (I found one just this morning by accident.)

As always, feedback is encouraged and appreciated. If you come across any bugs, please don't hesitate to file a report. If it's something that I feel is unrelated to Qt, I'll get on it. If I feel that it is related, I'll test it when Qt 4.8.7 is released and properly integrated.

Thanks for testing Armory! We really appreciate it.

[TimS]

Using 0.92.99.1 on Windows 7.
I started Armory with the following command line (D:\Armory does not exist yet):
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\bitcoin" --datadir="D:\Armory" --supernode
Without showing any error message, Armory opened using %appdata%\Armory as its data directory.
If I create D:\Armory first, it works as expected.

I expected that it would create the directory. If it can't/won't do that for some reason, I'd at least expect that it told me so, instead of silently falling back to the other location (not least because that's an SSD where space is too precious for something like this).

[etotheipi]

Using 0.92.99.1 on Windows 7.
I started Armory with the following command line (D:\Armory does not exist yet):
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\bitcoin" --datadir="D:\Armory" --supernode
Without showing any error message, Armory opened using %appdata%\Armory as its data directory.
If I create D:\Armory first, it works as expected.

That's actually a long-standing bug with Armory...  if the datadir doesn't exist, it uses the default.  I've wanted to fix it for like a year, but I guess it never quite hit priority.

[TimS]

That's actually a long-standing bug with Armory...  if the datadir doesn't exist, it uses the default.  I've wanted to fix it for like a year, but I guess it never quite hit priority.

Ok. It's still far from a critical bug, but it is an annoying bug that people are a little more likely to run into when upgrading to this version (since the DB isn't compatible, people might want to pick a new location). Any chance it'll make it into this release?

Another thing:

Spacing here could be better.

And speaking of issues like that, I submitted a pull request a while ago reporting some minor typos. The typos are still in the source. Can they be fixed for this release?

[helgabutters]

1) Can't export Log File. On a new Linux install, Core 0.10.0 and in Supernode go to "File" > "Export Log File" > "OK"

(DEBUG) ArmoryQt.py:4038 - exportLogFile
(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 4049, in exportLogFile
    if self.logFilePrivacyWarning(wCancel=True):
  File "/usr/lib/armory/ArmoryQt.py", line 4132, in logFilePrivacyWarning
    review."""), wCancel=wCancel, yesStr="&Ok")
  File "/usr/lib/armory/qtdefines.py", line 477, in MsgBoxCustom
    dlg = dlgWarn(wtype, title, msg, wCancel, yesStr, noStr)
  File "/usr/lib/armory/qtdefines.py", line 408, in __init__
    super(dlgWarn, self).__init__(None)
TypeError: __init__() takes exactly 3 arguments (2 given)

Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 4049, in exportLogFile
    if self.logFilePrivacyWarning(wCancel=True):
  File "/usr/lib/armory/ArmoryQt.py", line 4132, in logFilePrivacyWarning
    review."""), wCancel=wCancel, yesStr="&Ok")
  File "/usr/lib/armory/qtdefines.py", line 477, in MsgBoxCustom
    dlg = dlgWarn(wtype, title, msg, wCancel, yesStr, noStr)
  File "/usr/lib/armory/qtdefines.py", line 408, in __init__
    super(dlgWarn, self).__init__(None)
TypeError: __init__() takes exactly 3 arguments (2 given)

2) On Windows it correctly displays "You are using the latest version of core Bitcoin (0.10.0)" while on Linux using 0.10.0 gives "Core Bitcoin version 0.9.3 is available [Secure Downloader]"

Linux:
https://i.imgur.com/wn4jnR8.png

Windows:
https://i.imgur.com/jYTCXhh.png

[justusranvier]

   - Supernode Mode
        Use the "--supernode" flag before creating the databases to create
        a supernode database that enables instant address & wallet import.
        This is an enabling feature for high-volume, consumer facing apps
        and services to be built on Armory, such as exchanges and block-
        explorers.  NOTE: Running with --supernode will result in an Armory
        database approximately double the size of the blockchain!

It would be nice to have the option to configure this in the Settings page, as well as --skip--announce-check.

[Carlton Banks]

Is deterministic signing fully implemented? Is the deterministic signing code coming from libsecp256k1?

[goatpig]

Is deterministic signing fully implemented? Is the deterministic signing code coming from libsecp256k1?

Yeah it's fully implemented and set by default. We still use cryptopp only

1) Can't export Log File. On a new Linux install, Core 0.10.0 and in Supernode go to "File" > "Export Log File" > "OK"

Translation tags (tr()) have introduced some bugs, we'll get on top of it

[zombieslayer9099]

Found 1 minor bug, 1 major bug

http://prntscr.com/5qqia5
Notice the HTML code not working

I also believe the time prediction for building databases, etc. is bugged. It always starts at an outrageous time(ie. 2 months), then moves down to something more reasonable(ie. 6 hours)

Then it hangs. It uses no memory, no CPU, and barely any I/O. And the time prediction starts going up slowly, and when it does use I/O, it only reads at ~1% the speed it did before and there is no progress indicator in the logs, it's frozen.

Also noticed this:

Code:

2015-01-10 09:56 (INFO) -- ArmoryQt.py:2377 - loadBlockchainIfNecessary
2015-01-10 09:56 (ERROR) -- ArmoryQt.py:1220 - 8 attempts to load blockchain failed.  Remove mempool.bin.

'8 attempts' used to be '7 attempts' and '6 attempts' and so on. It does that every time, and number of attempts goes up by 1 or 2.

After it finishes going into its "hanging" state, it starts up again, then it hangs again, then starts up. This I can tell because of the time indicator, it went from 5 days to 3 days, then started going back up again! Meanwhile I noticed a 'blocks' file in the databases directory, based on the name I'll assume block data is inside it.
Well, there's one more thing -

http://prntscr.com/5qr55d
http://prntscr.com/5qr70x

If blocks is 600+ MB, and growing I might add, why does the progress bar not show it? Is the progress bar bugged, or is something wrong with Armory blockchain manager?

At the time of this edit, I am performing a factory data reset, and will see if this fixes the issue.

Edit: Factory data reset has not fixed the issue but Armory isn't hanging as bad as it was before, it's now using 4% of one CPU core, and 1 KB/s network bandwidth(both ways), also writing to disk which is a tiny bit of an improvement but not really noticeable, and I don't think it's Bitcoin Core causing this, so for the time being Armory is stuck with no databases, it seems.

I will leave Armory on for a few hours and see if anything happens, I hope it actually starts to build DB, currently 'blocks' file is at 576 MB and doesn't seem to be growing or shrinking at all.

Edit: Armory is reading block files, but it's not reading the full blockchain?

Code:

-INFO  - 1420907257: (BlockUtils.cpp:1115) Left off at file 0, offset 0
-INFO  - 1420907257: (BlockUtils.cpp:1118) Reading headers and building chain...
-INFO  - 1420907257: (BlockUtils.cpp:1119) Starting at block file 0 offset 0
-INFO  - 1420907257: (BlockUtils.cpp:1121) Block height 0
-DEBUG - 1420907263: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO  - 1420907270: (BlockUtils.cpp:1236) Loading block data... file 0 offset 0
-INFO  - 1420907300: (BlockUtils.cpp:384) Reading raw blocks finished at file 0 offset 134214363
-INFO  - 1420907804: (BlockUtils.cpp:384) Reading raw blocks finished at file 1 offset 134196904
-INFO  - 1420908772: (BDM_mainthread.cpp:273) Stop requested detected
-INFO  - 1420908772: (BDM_mainthread.cpp:316) UI asked build/scan thread to finish

Blank space

Code:

-WARN  - 1420908851: (BlockUtils.cpp:1102) --- Fetching SSH summaries for 853 registered addresses
-INFO  - 1420908851: (BlockUtils.cpp:1115) Left off at file 216, offset 96791440
-INFO  - 1420908851: (BlockUtils.cpp:1118) Reading headers and building chain...
-INFO  - 1420908851: (BlockUtils.cpp:1119) Starting at block file 216 offset 96791440
-INFO  - 1420908851: (BlockUtils.cpp:1121) Block height 338363
-DEBUG - 1420908852: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO  - 1420908855: (BlockUtils.cpp:1236) Loading block data... file 2 offset 101076734

Later:

Code:

-INFO  - 1420910479: (BlockUtils.cpp:1119) Starting at block file 216 offset 97937840
-INFO  - 1420910479: (BlockUtils.cpp:1121) Block height 338365
-DEBUG - 1420910479: (Blockchain.cpp:208) Organizing chain w/ rebuild
-INFO  - 1420910866: (BlockUtils.cpp:1236) Loading block data... file 3 offset 18312341

Edit: Resetting settings and such seemed to work, but Armory is loading outrageously slowly.

Code:

-INFO  - 1420910866: (BlockUtils.cpp:1236) Loading block data... file 3 offset 18312341
-INFO  - 1420912097: (BlockUtils.cpp:384) Reading raw blocks finished at file 3 offset 134192403
-INFO  - 1420914089: (BlockUtils.cpp:384) Reading raw blocks finished at file 4 offset 134210742
-INFO  - 1420916448: (BlockUtils.cpp:384) Reading raw blocks finished at file 5 offset 134193056
-INFO  - 1420918446: (BlockUtils.cpp:384) Reading raw blocks finished at file 6 offset 134187986
-INFO  - 1420920724: (BlockUtils.cpp:384) Reading raw blocks finished at file 7 offset 134176596
-INFO  - 1420923062: (BlockUtils.cpp:384) Reading raw blocks finished at file 8 offset 134212542
-INFO  - 1420925461: (BlockUtils.cpp:384) Reading raw blocks finished at file 9 offset 134199478
-INFO  - 1420927585: (BlockUtils.cpp:384) Reading raw blocks finished at file 10 offset 134015756

I've done some math, here are the times with some predictions:

Loading file 3 - 20:31, full file would have taken 23:19 based on prediction
Loading file 4 - 33:12
Loading file 5 - 39:19
Loading file 6 - 33:18
Loading file 7 - 37:58
Loading file 8 - 38:58
Loading file 9 - 39:59
Loading file 10 - 35:24

Average(excluding file 3) is 36:53 minutes per file, with a total of 217 files to process!
At this rate, it would take 5 days, 13 hours, and 23 minutes!
I have 16 GB of RAM, running on OS X 10.10, and have an SSHD installed(plan on dedicating an SSD of ~256 GB to Armory/Core), SSHD can write/read at about 85 MB/s. I don't know why Armory doesn't use at least half of what it used before(65.5 MB/s)

[helgabutters]

1) Can't create Single-Sheet SecurePrint(TM) paper backups. "Wallet Properties" > "Backup This Wallet" > Printable Paper Backup Single-Sheet "Create Paper Backup" > "Use SecurePrint(TM)"

2015-01-10 08:31 (INFO) -- qtdialogs.pyc:7056 - Deriving SecurePrint code took 0.42 seconds
2015-01-10 08:31 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 7219, in redrawBackup
  File "qtdialogs.pyc", line 7397, in createPrintScene
  File "qtdialogs.pyc", line 6956, in drawColumn
  File "qtdefines.pyc", line 25, in tr
  File "encodings\utf_8.pyc", line 16, in decode
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2122' in position 26: ordinal not in range(128)

https://i.imgur.com/ePwRD38.png

2) Can't create Fragmented SecurePrint(TM) paper backups. "Wallet Properties" > "Backup This Wallet" > Printable Paper Backup Fragmented "Create Paper Backup" > "Use SecurePrint(TM)" > "Print All Fragments"

2015-01-10 08:40 (INFO) -- qtdialogs.pyc:7056 - Deriving SecurePrint code took 0.38 seconds
2015-01-10 08:40 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 12111, in clickPrintAll
  File "qtdialogs.pyc", line 12126, in clickPrintFrag
  File "qtdialogs.pyc", line 7164, in __init__
  File "qtdialogs.pyc", line 7215, in redrawBackup
  File "qtdialogs.pyc", line 7410, in createPrintScene
  File "qtdialogs.pyc", line 6956, in drawColumn
  File "qtdefines.pyc", line 25, in tr
  File "encodings\utf_8.pyc", line 16, in decode
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2122' in position 40: ordinal not in range(128)

2a) Same as 2 but selecting a single "View/Print"

2015-01-10 08:41 (INFO) -- qtdialogs.pyc:7056 - Deriving SecurePrint code took 0.34 seconds
2015-01-10 08:41 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 12086, in <lambda>
  File "qtdialogs.pyc", line 12126, in clickPrintFrag
  File "qtdialogs.pyc", line 7164, in __init__
  File "qtdialogs.pyc", line 7215, in redrawBackup
  File "qtdialogs.pyc", line 7410, in createPrintScene
  File "qtdialogs.pyc", line 6956, in drawColumn
  File "qtdefines.pyc", line 25, in tr
  File "encodings\utf_8.pyc", line 16, in decode
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2122' in position 40: ordinal not in range(128)

3) When sending bitcoins and you input an invalid address (or no address) you get a not properly filled in error box.

https://i.imgur.com/RplqPH2.png

[jammers]

Hi guys,

I use Win 8.1 and 64bit bitcoin core.

Digitally backed up my wallets, the uninstalled bitcoin and armory, and deleted manually all the files, to give it close to a clean install.

Installed armory fine, but then skipped importing a wallet. So I know bitcoin isn't installed yet. Clicked Check again, and get this

Screen I'm talking about



Visual bug




I also found a second similar case

Going into settings, and trying to set it as the default bitcoin handler





So similar to the bug reported by TimS

Also, when in settings, and clicking the ? pop up over the default fee, this is muddled up too



Similar visual bug, this time via Help | Clear all confirmed



Similar visual bug via Help | Rescan databases



Same for Help | Rebuild & Rescan



Next, when I click help | armory version,

this little progress indicator pops up, but does nothing.



Also, this a group of similar minor bugs

In the dashboard screen, where there's the text, the frequently asked question link doesn't work. Links to https://bitcoinarmory.com/faqs/

But that doesn't work



Same goes for the "armory backups page" link, which is sending to https://bitcoinarmory.com/armory-backups-are-forever/ and again getting page not found

Same goes for the "armory quick start guide" link, which is sending to https://bitcoinarmory.com/using-our-wallet and gives page not found.

Same for "offline wallet tutorial", which is sending to https://bitcoinarmory.com/using-our-wallet/#offlinewallet and gives page not found.

So basically none of these links work.

Finally, on this section, there's a massive block of grey blank space underneath all the text. Just a bit unnecessary

Also, you're using wordpress on your site. so you're front door at http://bitcoinarmory.com/wp-admin is wide open.



You should really install something like "all in one wordpress security and firewall plugin" (https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)  and enable brute force protection to rename this to a secure login url, plus put in captchas, honeypots etc. I'm sure that URL will get blitzed, and if someone got in that way they could just change the website to point to a malicious file. PM me and I can guide you through this if you want, takes about twenty minutes to implement, and will block out a lot of shit in the first place.

I then asked to switch to expert mode on reboot, and disabled torrent downloading ( to see if new header thing is working), and installed the 0.10 bitcoin client, and opened up armory. So these were while it was initialising bitcoin engine

I then checked in the advanced mode, and noticed that multisig | lockbox manager, the lockbock documentation doesn't link anywhere



While still scanning, if i click multisig | simulfund promissery note, I get this



Similar if I do multisig | simulfund collect and merge and then click create and add a promisary note



If I hit cancel here, I also get this



Also, if I go into multisig | simulfund review and sign, don't select anything, but hit done, I get this



This isn't a bug, but the "Please note" message where it mentions the size needed needs to be updated/doubled!



Also, it's all time based in the countdown, but I noticed it near the end



For this whole sync time, couldn't you just show people how many blocks it's at and going through? People will understand the wait if they can see that there's hundreds of thousands of blocks going through. And numbers continually reducing is way better than time that doesn't make sense.

Cheers

Jamie

P.S. Just a note from games, trying to figure out what was where when we were localising games from asia into english, and then into other languages, where we had the UI and text fields coming from all over the place.

For debugging builds, you can append a number/hex code to each text field in the UI and error messages (both titles and content). If an error message comes up, it makes it easier to highlight where the field needs to be changed. Also, if you have an error message, and we trigger it when testing, we can give suggestions for better text.

ie. in this



Instead of "The Bitcoin software still appears to be missing. If you just installed it, then please adjust your settings to point to the installation directory"

it would be a lot more noob friendly if it said

"Bitcoin Armory has not detected the Bitcoin Core software installed in it's standard installation directory. To fix this, click Menu | Settings. On that screen, set the Bitcoin Core installation directory, and the Home Directory. Click save, reboot Armory and try again."

[TimS]

Especially important for our more-hardcore users, we now have a "supernode" mode, that doubles Armory's DB size, but indexes all scripts on the blockchain.  If you delete your databases and start Armory with "--supernode", you'll build a DB that does instant importing of addresses and wallets.  It could be used to build a block explorer or an Electrum-style server for feeding lite-nodes (for everyone who's asked about lite-Armory, completion of supernode was a critical milestone that needed to be crossed to even think about it).
        

   - Improved armoryd.py
        The daemon version of armory, armoryd.py, has been fully updated and
        tested with the new database engine.  Also includes a new "webshop"
        sample application that demonstrates basic usage of armoryd.py to
        collect & verify payments, generate unsigned transactions, etc.

I'm interested in having my own private Armory-powered block explorer. Where can we find armoryd.py and "webshop"? Does armoryd.py work on Windows, and is there anything special that needs to be done to set it up?

[TimS]

Ubuntu 14.04, when hovering the colors in the tooltip are dark and nearly unreadable; if you click on the (?), it changes to a readable lighter background.




The tooltip above says "Change Encryption", which doesn't match the actual button that says "Encrypt Wallet". Also, the tooltips for Wallet Name and Description have "Change Labels" instead of "Change Wallet Labels".

[helgabutters]

Just to have some minor clarification, would the visual bugs above all count separately? Most of them seem to be the same general issue but just in lots of different places. If so, I have some more hunting to do

[helgabutters]

1) Putting a " in the "Label" section of "Create Payment Request Link" blanks the output

"Receive Bitcoin" > "Create Clickable Link" and in the Label type: testing"

https://i.imgur.com/8VoGR1p.png

2) In "Recieve Bitcoin" > "Manually Enter "bitcoin:" Link", if the value following in "amount=" is not just a number and you hit "Done" you get no message/error box and the below is the log.

The link I used was "bitcoin:n2vPVmUbFBmXNa4uwX45dzCjFx4cXcd58V?amount=p32&label=fewafew"

2015-01-10 11:30 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 10616, in clickedOkay
  File "ArmoryQt.py", line 2490, in parseUriLink
  File "armoryengine\ArmoryUtils.pyc", line 2894, in parseBitcoinURI
  File "armoryengine\ArmoryUtils.pyc", line 1292, in str2coin
ValueError: invalid literal for int() with base 10: 'p32'

3) When "Sending Bitcoin" there is no max length for the comment like there is in the "Transactions" tab in the main window. I put the following string in the comment (alphabet + num at the end so you can see where in the string you are):
abcdefghijklmnopqrstuvwxyz1abcdefghijklmnopqrstuvwxyz2abcdefghijklmnopqrstuvwxy z3abcdefghijklmnopqrstuvwxyz4abcdefghijklmnopqrstuvwxyz5abcdefghijklmnopqrstuvw xyz6abcdefghijklmnopqrstuvwxyz7abcdefghijklmnopqrstuvwxyz8abcdefghijklmnopqrstu vwxyz9abcdefghijklmnopqrstuvwxyz10abcdefghijklmnopqrstuvwxyz11abcdefghijklmnopq rstuvwxyz12abcdefghijklmnopqrstuvwxyz13abcdefghijklmnopqrstuvwxyz14abcdefghijkl mnopqrstuvwxyz15abcdefghijklmnopqrstuvwxyz16abcdefghijklmnopqrstuvwxyz17abcdefg hijklmnopqrstuvwxyz18abcdefghijklmnopqrstuvwxyz19abcdefghijklmnopqrstuvwxyz20ab cdefghijklmnopqrstuvwxyz21abcdefghijklmnopqrstuvwxyz22abcdefghijklmnopqrstuvwxy z23abcdefghijklmnopqrstuvwxyz24abcdefghijklmnopqrstuvwxyz25abcdefghijklmnopqrst uvwxyz26abcdefghijklmnopqrstuvwxyz27abcdefghijklmnopqrstuvwxyz28abcdefghijklmno pqrstuvwxyz29abcdefghijklmnopqrstuvwxyz30abcdefghijklmnopqrstuvwxyz31abcdefghij klmnopqrstuvwxyz32abcdefghijklmnopqrstuvwxyz33abcdefghijklmnopqrstuvwxyz34abcde fghijklmnopqrstuvwxyz35abcdefghijklmnopqrstuvwxyz36abcdefghijklmnopqrstuvwxyz37 abcdefghijklmnopqrstuvwxyz38abcdefghijklmnopqrstuvwxyz39abcdefghijklmnopqrstuvw xyz40

4) Num 3 also creates a display bug. When you are looking at the "Transactions" tab in the main window, if you double-click to expand out the "Comment" section to display the full comment the navigation bar won't let you see the whole comment. There seem to be 5 spots that the navigation bar sticks to where the first four are small moves and the last one just jumps to the end.

Fourth Spot:
https://i.imgur.com/SNjxFoN.png

Fifth/Final Spot:
https://i.imgur.com/iEdPnRs.png

5) In "Receive Bitcoins" you can't double click the QR code to expand. It also seems to happen anywhere else there is a QR code that needs to be double clicked. This is the log:

2015-01-10 13:15 (ERROR) -- Traceback (most recent call last):
  File "qtdefines.pyc", line 811, in mouseDoubleClickEvent
  File "qtdefines.pyc", line 817, in __init__
TypeError: __init__() takes exactly 3 arguments (2 given)

[jammers]

where do those logs come from?

[helgabutters]

where do those logs come from?

If you are using testnet then look at the following:

Windows - C:\Users\Username\AppData\Roaming\Armory\testnet3\armorylog.txt
Linux - /home/username/.armory/testnet3/armorylog.txt

(AppData is usually hidden on Windows so you'll need to "Show hidden files, folders, and drives" through the folder options)

[jammers]

I'm just using the normal version, not a testnet one.

I'll just document what I can so it can be easily replicated !

[jammers]

I also believe the time prediction for building databases, etc. is bugged. It always starts at an outrageous time(ie. 2 months), then moves down to something more reasonable(ie. 6 hours)

+1

Would be better to have no time, than a time that just isn't true. Maybe have some sort of animation that builds up over time as the blockchain is assembled? The % is fine, but the time value never made sense in any version.