[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]

[etotheipi]

Make some money helping test the new version of Armory (0.89.99-testing)!

Download 0.89.99.14: Windows (32- and 64-bit)
Download 0.89.99.14: Ubuntu/Debian 32-bit
Download 0.89.99.14: Ubuntu/Debian 64-bit
Download 0.89.99.14: Mac/OSX (not very usable in 10.9)



For anyone who's been waiting for the new version of Armory, we're almost there!  But we desperately need more testing.   I tested this bug-bounty idea about a year ago, and it seemed to work pretty well.  Besides bugs, Armory got a ton of polishing, too.  So let's try this again!  If you want to claim a full 0.04 BTC (about $17 USD at the time of writing):

• (1) You must be the first to post the buggy behavior.  If there's an error in the log file, you must copy that error here.
• (2) The bug must be reproducible by me and impact the usability or security in a non-negligible way (things like grammatical error or sub-optimal design choices are welcome, but won't be rewarded with BTC)
• (3) Certain categories of bugs, along with already-known issues are not rewarded (the list is at the end of this post)
• (4) I get the final word in who receives a bounty and how much.  Double-bounties and partial-bounties are possible
• (5) I will cap the payouts to 1 BTC total.  If this is productive, I'll happily increase the limit.  
• (6) You are expected to know how to run and use Armory already.  It's an advanced tool with a bit of a learning curve.  This space is not for teaching you how to use it.  (there's an Armory sub-forum for that).
• (7) Not responsible for lost Bitcoins (though I've never seen even a hint of a problem that would lead to loss of coins).  To use it on testnet, you may have to run Bitcoin-Qt yourself and unselect the first checkbox in the Armory settings window.  Remember that Armory uses "--testnet", Bitcoin-Qt/bitcoind uses "-testnet"

This offer ends at 11:59pm EST, Nov 23, 2013!

The following is a list of new features in Armory.  Yeah, there's a lot!  Please test all aspects of the application, though you might be more likely to find bugs in these new features:

• RAM usage and startup time reduction: RAM reduced to less than 300MB, and startup time typically under 60 seconds after initial DB build!
• Persistent database: Armory now maintains its own blockchain database for fast startup.  Make sure you have space to duplicate the blockchain (will be reduced in a subsequent version; this way was easier for now).
• Full MacOSX support: thanks to picobit for the builder, though the Apple+PyQt bugs prevent full usability in 10.9.  Only accepting bug reports in OSX 10.8.
• New Backup Center:  Better organization and description of backup options.  Includes unencrypted digital backups, now.
• Fragmented Backups:  Shamir's Secret Sharing (M-of-N secret splitting); balance your physical security and redundancy.  Create up to 5-of-6 backups in Standard & Advanced modes.  Up to 8-of-12 in Expert mode.  Fragments are also deterministic for a given M value.  For example, if you make a 3-of-5 backup, you can later make a 3-of-7 and the first 5 will be the same as the 3-of-5
• SecurePrint: Paper backups optionally encrypted with code on screen to prevent private key exposure to printer and other network devices.  SecurePrint code should be identical across all backup types for a given wallet
• Half-sized paper backups:  The chaincode is now derived from the private key, meaning only two lines of data for wallets created with the new version of Armory.  Yet, all backup features work with older wallet without a hitch -- they'll all show four lines (if you don't believe me, prove me wrong and collect your 0.04 BTC!)
• Paper backup tester: test any kind of paper backup before you bury it in your backyard.  Includes subset testing of fragmented backups.
• Message Sign & Verify: Finally Bitcoin-Qt-compatible signing and verification.  Will have a new ASCII-armored version like PGP signing, soon
• Fixed broadcasting non-std signatures:  Older versions of Armory produced signatures that have non-standard padding.  If an older version is used on your offline system, you can't broadcast those signed transactions with 0.88.1 online.  This version will fix the padding and broadcast successfully
• Improve *nix Makefile:  Improved Makefile that should work out of the box on most Linux distros once the proper depedencies are installed.  See the osx_picobit directory for compiling on OSX.

As a reminder, here's some pre-existing features that would benefit from testing:

• Importing & sweeping of private keys.  Single and multi.
• Creating deterministic wallets with customizable unlock time/RAM.
• Restoring paper and digital backups without restarting the app
• Coin control (in Expert usermode)
• Customizable change addresses
• "bitcoin:" URI-handling (with known deficiency on some Linux distros)
• "File" -> "Export Transaction History"
• OFFLINE WALLETS (no offline bundle for this version yet)

Claimed:

whault:  1 x bounty (key calculator not removed)
duxZero:  1 x bounty (tool tips and squashed buttons)
jyyst:  1 x bounty (unicode issues)
simonL: 1 x bounty (corrupt wallet file confusion)
Cyberdyne:  1 x bounty (lingering sys tray icon)
idoB:  1 x bounty (links, grammar and backup fields)
cp1:  2 x bounty (confusing --datadir DNE behavior)
devthedev:  1 x bounty (bad autoscrolling of dashboard)

flipperfish:  1x for the "Send Bitcoins" first five entries bug (I knew about that one... long story)
PRab:  1x for the lots of little issues:  (4 time pwd asking, focus issues, let user choose backup)
greBit:  1x for shutdown hanging (I think this is fixed now, isn't it?)
Zomdifros: 1x for... I don't know what that error is... sending issues... definitely a bug!
elbandi:  1x for UAC issues (will be fixed in 0.91)
tc23emp:  1x for maxConnections error (I've been looking for the src of that bug!  Thanks!)

[1715410370]

1715410370

[1715410370]

1715410370

[1715410370]

1715410370

[etotheipi]

Here's a list of things that are already known that do not qualify for a bounty:

• Yes, Armory requires having the whole blockchain.  Yes, it requires running Bitcoin-Qt in the background.  Yes, sometimes it's difficult to point Armory to the correct bitcoind location.  Yes, Armory now duplicates the blockchain data (will be reduced in the next version...this way was simpler for the overhaul).  Most reports related to general setup will be unrewarded.
• Bugs in online mode must be reported after a full synchronization.  I don't need help finding synchronization/setup bugs (I get plenty of emails).  All bugs assume you are in either in offline mode or fully sync'd in online mode.  
• I know the auto-install bitcoind buttons don't work
• The app initiates a rescan on unclean shutdown.  Yeah, it's kinda slow on mainnet.  Shutdown cleanly as much as possible
• Fee calculations.  Max tx size.  Min tx value.  I know they're outdated.  I will fix them soon.
• The new version is not very usable on OSX 10.9.  I can only accept bugs for 10.8 and lower.  If you run in 10.9,  compare your error messages to this before reporting.  These are actually Apple+PyQt bugs, not mine.
• In some Linux distros/environments, URI-handling is broken.  I can tell you how to fix it if needed.  Should work in Ubuntu+Unity, as well as all Windows verisons.
• WinXP support is hosed.  Goatpig is trying to figure that one out...
• Occasionally the DB gets corrupted and automatically rebuilds.  It takes a while.  And may be inconsistent.  Yeah, it sucks.
• Key Calculator and EC Calculator are both off-limits.  Key calc was meant to be removed, and EC calc is both only for expert users and not very maintained (though it technically works if you have the screen space for it).

I will not be maintaining this list for every reported bug.  You may have to read subsequent posts to find out what's been reported.  Or just post your bug and I'll tell you if I fixed it yet.


Usage notes:

This version maintains a full database between loads.  If you find yourself with incorrect balances or corrupted DB errors, you can use the "Help" menu to reset the DB.  A rescan typically takes about 10-20 min.  A rebuild takes 30-90 minutes followed by the rescan.  I'd like to think this will largely be unnecessary, but it's always useful to someone.

Similarly, you can run with " --rescan" or "--rebuild" on the command line.  Or if you're desperate (or on OSX where CLI options don't work), you can simply "touch ~/.armory/rebuild.txt" or "touch ~/.armory/rescan.txt".  Also "touch ~/.armory/clearmempool.txt" will remove stuck transactions.

[whault]

OSX 10.9, general feeling is that the app is not ready for prime-time. There's a number of crashes that I've encountered, this is the only one I can reliably trigger though.

Print wallet:

Opening "wallet properties" > "backup this wallet" > "create paper backup" will open a standard OSX print window, after about two seconds the window loses focus and will ignore all clicks. Clicking a button before the window loses focus will sometimes cause Armory to crash.


https://i.imgur.com/sVgSxwu.gif

[etotheipi]

OSX 10.9, general feeling is that the app is not ready for prime-time. Almost constant crashes, for which I only know a couple of the triggers.

Can you please run from the terminal and confirm that the printed error messages look like this:

modalSession has been exited prematurely - check for a reentrant call to endModalSession

From the terminal, you can just "cd /Applications; open Armory.app"

[whault]

From the terminal, you can just "cd /Applications; open Armory.app"

You probably want to direct users to run this instead:

Code:

/Applications/Armory.app/Contents/MacOS/Armory

The command you have will execute the app but not print any log output back to the terminal.

Can you please run from the terminal and confirm that the printed error messages look like this:

There's a lot of output like that, mainly when in the wallet properties view.

Code:

2013-11-15 14:18:28.350 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:28.830 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:28.846 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:28.847 Python[22287:507] -[NSApplication runModalSession:]: Use of freed session detected. Do not call runModalSession: after calling endModalSesion:.
2013-11-15 14:18:38.313 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:38.328 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:

For the crash in the print dialogue:

Code:

/Applications/Armory.app/Contents/MacOS/Armory: line 16: 22555 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py

The full crash log has been DM'd to you.


EC Calculator:

The labels in this view are a little squashed:

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

Clicking the "address book" icon to select a private key hangs the app.

Code:

(ERROR) armoryengine.py:12767 - Waited 20s for addrbook to be returned.  Abort
(ERROR) armoryengine.py:12768 - ID: getTxByHash (86700430)
(ERROR) Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10549, in execAddrBook
    dlg = DlgAddressBook(parent, parent.main, targWidget,  defaultWlt, actionStr, selectExistingOnly, selectMineOnly)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10213, in __init__
    self.setAddrBookTxModel(defaultWltID)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10340, in setAddrBookTxModel
    self.addrBookTxModel = SentToAddrBookModel(wltID, self.main)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armorymodels.py", line 807, in __init__
    for abe in TheBDM.getAddressBook(self.wlt.cppWallet):
TypeError: 'NoneType' object is not iterable

Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10549, in execAddrBook
    dlg = DlgAddressBook(parent, parent.main, targWidget,  defaultWlt, actionStr, selectExistingOnly, selectMineOnly)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10213, in __init__
    self.setAddrBookTxModel(defaultWltID)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10340, in setAddrBookTxModel
    self.addrBookTxModel = SentToAddrBookModel(wltID, self.main)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armorymodels.py", line 807, in __init__
    for abe in TheBDM.getAddressBook(self.wlt.cppWallet):     
TypeError: 'NoneType' object is not utterable

Sometimes after a crash when doing a full rescan, the app will crash out again with the output:

Code:

-ERROR - 1384487000: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
-ERROR - 1384487000: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
/Applications/Armory.app/Contents/MacOS/Armory: line 16: 23075 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py

This crash log has been DM'd to you as well.

[etotheipi]

@whault:

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.  

EC & Key Calculators:  Ack!  The Key calculator was meant to be gone, and I normally would've specified that it's off-limits for bug bounties.  But I'll give you a bounty for it, because it is a bug that it's still there!  I need to remove it.

I will update the top post to specify that both key calculator and EC calculator are off-limits for bug bounties, and key calc will be removed.

[whault]

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.

The print issue predates Mavericks, I can replicate it on 10.8 in both the latest stable and the latest beta.

I completely understand your reluctance to support 10.9, it's foreign territory especially as you're not a native developer.

[etotheipi]

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.

The print issue predates Mavericks, I can replicate it on 10.8 in both the latest stable and the latest beta.

I completely understand your reluctance to support 10.9, it's foreign territory especially as you're not a native developer.

Oh, that's right... I do remember having to do some special stuff on OSX with the print dialog.  But I seem to remember that it was fixed with the OSX-specific code... I guess not?

[jl2012]

Is it BIP32 compliant?

[etotheipi]

Is it BIP32 compliant?

Negative.  That's a whole different overhaul, and it would be a total mess to do that overhaul at the same time as this one.

After this release will be a bug-fix and polishing release (like fixing unicode issues, and re-optimizing the database engine).  Then, I'll finish the new wallet format (which is like 75% done already), and that will come with support for BIP 32, compressed public keys, and all the hooks for adding multi-sig. 

[whault]

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.

The print issue predates Mavericks, I can replicate it on 10.8 in both the latest stable and the latest beta.

I completely understand your reluctance to support 10.9, it's foreign territory especially as you're not a native developer.

Oh, that's right... I do remember having to do some special stuff on OSX with the print dialog.  But I seem to remember that it was fixed with the OSX-specific code... I guess not?

Seems not. You can open up the PDF preview and print from there if you are extremely fast (race against the window freezing), but if you manage it Armory will crash and lose it's working database.

[kdrop22]

Looking forward to the new version of the software. What is the tentative release date for the final version.

[SimonL]

Here's a bug I've found since the last stable version, I've tried this on 0.89.99.10-beta and 0.89.99.14-beta and I've done a couple rescans too. It seems for me the transactions tab does not populate until it receives a new block after it has finished loading. It pretty much seems to stay like and looks like it is broken until I left it running for a while and then suddenly all the transactions in the window appears, everything else seems to work fine though. This only seemed to happen the first time it was run so, it might be that everything is catching up the first time and it is taking a really long time to reorganise itself. It does report errors in the log though so here they are.

the log as follows:

Code:

2013-11-15 19:29 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2013-11-15 19:29 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-15 19:29 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-15 19:29 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-15 19:29 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2pD6iHKkB
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 35Fijn44X
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2H5X6XTGs
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: CSFC3QFR
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2ToSafqhH
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1919 - Current block number: 269713
2013-11-15 19:43 (INFO) -- armoryengine.py:10634 - Received new block.  0000000000000004f6512bbfeccd904fa068123e33d59211253bbd307c54f441
2013-11-15 19:44 (INFO) -- armoryengine.py:10634 - Received new block.  0000000000000004fe7b45f3bbc4c7edbd9ff86c963fe77282453e1b38f66503
2013-11-15 20:12 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-15 20:12 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-15 20:12 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-11-15 20:12 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-11-15 20:12 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (64639402)
2013-11-15 20:12 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ReadBlkUpdate (64639402)
2013-11-15 20:12 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-11-15 20:12 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2013-11-15 20:15 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-11-15 20:15 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-11-15 20:15 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (35311268)
2013-11-15 20:15 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ReadBlkUpdate (35311268)
2013-11-15 20:15 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-11-15 20:15 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2013-11-15 20:20 (INFO) -- ArmoryQt.py:4779 - New Block! : 269717
2013-11-15 20:20 (INFO) -- ArmoryQt.py:4803 - Current block number: 269717

And how it looked when the error in the log appeared.

[picobit]

Oh, that's right... I do remember having to do some special stuff on OSX with the print dialog.  But I seem to remember that it was fixed with the OSX-specific code... I guess not?

The print dialog works for me (OS X 10.9) - and at some point it started to work for me in 10.8, too.

[duxZero]

Your (?) tool tips require you to click, hold and drag the mouse off the tool tip to keep it displaying else as soon as you just click it disappears.

--

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

[Mooshire]

I'm on it, Windows 8

[jyyst]

I have got still problem with no ascii, national characters(like ążźć) in label of address.

Code:

(ERROR) Traceback (most recent call last):
  File "/home/piotrek/Apps/BitcoinArmory/qtdialogs.py", line 2198, in acceptNewAddr
    comm = str(self.edtComm.toPlainText())
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)

Traceback (most recent call last):
  File "/home/piotrek/Apps/BitcoinArmory/qtdialogs.py", line 2198, in acceptNewAddr
    comm = str(self.edtComm.toPlainText())
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)

The problem is not new but it still appears so i don't want reward.

[etotheipi]

I have got still problem with no ascii, national characters(like ążźć) in label of address.

Ack, I was just about to add that to the list of off-limit topics.  I'm well aware of Armory's unicode issues, and fixing that is in my plans for the next release after this one.  Since it wasn't on the list, I'll give you the bounty for it.

Your (?) tool tips require you to click, hold and drag the mouse off the tool tip to keep it displaying else as soon as you just click it disappears.

This behaves differently in each OS.  I haven't yet figured out how to make this consistent and friendly.  Still better than the mouse-over-hold-wait-display, which some users didn't figure out.   Again, something else I meant to post as already-known, but I'm not going to be stingy about it.  You tested the interface and found a usability issue.  One bounty for you!

Here's a bug I've found since the last stable version, I've tried this on 0.89.99.10-beta and 0.89.99.14-beta and I've done a couple rescans too. It seems for me the transactions tab does not populate until it receives a new block after it has finished loading. It pretty much seems to stay like and looks like it is broken until I left it running for a while and then suddenly all the transactions in the window appears, everything else seems to work fine though. This only seemed to happen the first time it was run so, it might be that everything is catching up the first time and it is taking a really long time to reorganise itself. It does report errors in the log though so here they are.

Okay, so I haven't heard of this bug in a long time.  I thought it only happened when you have a corrupt wallet in your list.  If you isolate it better, I got a bounty for you!  What OS?  Can you try making a copy of the ARMORY_HOME_DIR (if you have the space for it), then remove the wallets, and run Armory with " --datadir=/new/directory/path".  Create a single new wallet, then restart and let it sync again.  I need to know if it goes away.  If so, then there's an issue with one of the wallets and I'll dig further.

[Mooshire]

Ok, so this isnt a bug, but a suggestion. The percentage complete when downLoading the blocks is really only helpful on the first download. When  i boot up Armory and it says 99% 10 minutes remaining, that doesnt tell me much. Maybe the percentage could be percentage complete since the beginning of the download, or you could include how many blocks behind the client is.

[cp1]

Yes, Armory requires having the whole blockchain.  Yes, it requires running Bitcoin-Qt in the background.  Yes, sometimes it's difficult to point Armory to the correct bitcoind location.

I know this is a known issue, but I'd suggest having a way to enter the satoshi directory in the settings.  When you click the "let armory run bitcoin", Bitcoin home directory could stay editable.  Or change to blockchain directory.

[etotheipi]

Ok, so this isnt a bug, but a suggestion. The percentage complete when downLoading the blocks is really only helpful on the first download. When  i boot up Armory and it says 99% 10 minutes remaining, that doesnt tell me much. Maybe the percentage could be percentage complete since the beginning of the download, or you could include how many blocks behind the client is.

Heh, ironic you mention that.  Because not long ago I had it the way you just mentioned, and people were pissed off that it looked like the whole thing was starting over from scratch.  Especially when they interrupted the initial DB build and restarted it.  I changed it from what you just requested, due to popular demand

Admittedly, maybe I can change the behavior when you're mostly synchronized already, versus in the middle of the huge DB build operation...

[Mooshire]

I'm not sure if this counts as a bug, but when I loaded up armory, it had to download the last 3% of the blockchain, then go through building the database, but now its scanning the blockchain. The problem is, the only wallet has 0 addresses and was freshly created. So now I'm stuck waiting while it scans for nothing.

[etotheipi]

I'm not sure if this counts as a bug, but when I loaded up armory, it had to download the last 3% of the blockchain, then go through building the database, but now its scanning the blockchain. The problem is, the only wallet has 0 addresses and was freshly created. So now I'm stuck waiting while it scans for nothing.

If there's zero addresses/wallets, it should skip the scan.  If it's a newly created wallet, the addresses should be marked "new" and not induce a rescan.

However, it will always rescan on an unclean shutdown.  It's a long story.  I'd rather that inconvenience occur than have corrupted balances/history and the confusion that follows.  However, it's probably robust enough to not require a rescan on unclean shutdown, I just haven't tried yet.

[Mooshire]

I freshly installed Armory, created a new wallet while it was downloading the blocks, and haven't quit it since. It's still scanning.

[etotheipi]

I freshly installed Armory, created a new wallet while it was downloading the blocks, and haven't quit it since. It's still scanning.

Just to be clear, when Armory starts up is using auto-bitcoind, it does the following:

(1) Starts bitcoind, requests its sync state
(2) Waits for bitcoind to finished downloading the 15GB blockchain
(3) Builds/updates the Armory databases from the 15GB of blk*.dat files produced by bitcoind
(4) Checks the stored address histories in the DB and compares against wallet addresses
(4a) If there are no addresses needing to be rescanned, it simply loads the histories
(4b) If the histories are incomplete, or you had an unclean shutdown (histories were never written to DB) -- rescans the full Armory databases
(5) Switches the interface to "online mode" and displays the tx history.

If your bitcoin-qt/bitcoind is already synchronized, then step #2 is minimal effort.  Otherwise it can take 4-48 hours depending on your connection (but you know that part). 

If you have not run Armory before, it will have to build the databases from scratch the first time in #3, which will take 30-120 minutes (on most systems).  If the DB is already built, it only updates the latest blocks (like 10 sec).

Step #4 either takes 5 sec (if already sync'd), or 10-30 minutes if it needs a full rescan.   This step will get much faster on the next release. 

If you did not add any addresses, or you did but they were part of a new wallet, then it should only have to do step #4 once.  After that, it will startup in like 30 sec.   If you see alternative behavior, it's probably a bug.

*The one exception to all of the above is the occasional DB corruption where it automatically detects and rebuilds.  Yes, annoying.  But I don't have any other way until I reduce the DB corruption events. 

[picobit]

Heh, ironic you mention that.  Because not long ago I had it the way you just mentioned, and people were pissed off that it looked like the whole thing was starting over from scratch.  Especially when they interrupted the initial DB build and restarted it.  I changed it from what you just requested, due to popular demand

Admittedly, maybe I can change the behavior when you're mostly synchronized already, versus in the middle of the huge DB build operation...

You clearly need two progress bars

One showing percent of total progress, the other showing percent of todays progress.

[duxZero]

For the bounty: 1LGBcGGi6aEgbnWtwfpBn3m4n4Js1gRxf8

Sorry i'm just wasting time test small things while i wait to get online.

Also, just a suggestion,
Bitcoin 'stealers' have a feature that when a bitcoin address is copied to the clipboard it is replaced with the 'hackers' address.
With saying that i think you should add a warning system to alert the user when this happens with any address's linked to Armory.

[whault]

Bitcoin 'stealers' have a feature that when a bitcoin address is copied to the clipboard it is replaced with the 'hackers' address.
With saying that i think you should add a warning system to alert the user when this happens with any address's linked to Armory.

If malware has enough access to change the contents of your clipboard, then verifying the contents of it will not in the slightest save your wallet.

[duxZero]

All the BTC 'stealers' do is steal the wallet and tamper with the clipboard.

If your actually getting RAT'ed then just lock down all the network connections and monitor the traffic.

As for key loggers just create an on screen keyboard for the application itself.

[etotheipi]

As for key loggers just create an on screen keyboard for the application itself.

Btw, Armory has this.  Click "Show Keyboard" when it asks you to type in your password.  Lots of crazy options for scrambling it, though they're not actually that useful (it's almost intolerable to type with a scrambled keyboard)

[duxZero]

Didn't even notice, my bad.

But yeah just a suggestion to offer a somewhat more advanced security lockdown to help 'prevent' malware.

[whault]

Didn't even notice, my bad.

But yeah just a suggestion to offer a somewhat more advanced security lockdown to help 'prevent' malware.

If your machine is compromised, nothing will save you from having the contents of your wallet stolen. Onscreen keyboards, "scrambling" and checking the clipboard are just feel-good measures and offer no tangible security. At best they offer some obscurity, but it's only a matter of time before Armory targeted methods arise.

[etotheipi]

Didn't even notice, my bad.

But yeah just a suggestion to offer a somewhat more advanced security lockdown to help 'prevent' malware.

If your machine is compromised, nothing will save you from having the contents of your wallet stolen. Onscreen keyboards, "scrambling" and checking the clipboard are just feel-good measures and offer no tangible security.

I don't promote the feature much, because it's minimal security improvement.  But it does protect against the simplest of keyloggers.  There's this notion that all viruses are omniscient, and targeting your bitcoin wallet.  If it's targeting your wallet, the OSD keyboard probably won't help.  But if it's just sucking data off your system looking for banking login passwords, etc... you avoided giving away too much info.

But I agree the feature is really quite minimal in terms of its security benefit.   (and generally, I try to assume omniscient malware when thinking about security, but not everything has to be super-effective to be part of the interface)

[Cyberdyne]

Here's a tiny non-critical bug that's been in every version of Armory I've tried.

On windows 7, when you exit Armory, the icon for it stays on the system tray until I mouse over the icon, then it will disappear.

This happens even with a normal, clean exit of the program.

[whault]

If your machine is compromised, nothing will save you from having the contents of your wallet stolen. Onscreen keyboards, "scrambling" and checking the clipboard are just feel-good measures and offer no tangible security.

I don't promote the feature much, because it's minimal security improvement.  But it does protect against the simplest of keyloggers.  There's this notion that all viruses are omniscient, and targeting your bitcoin wallet.  If it's targeting your wallet, the OSD keyboard probably won't help.  But if it's just sucking data off your system looking for banking login passwords, etc... you avoided giving away too much info.

But I agree the feature is really quite minimal in terms of its security benefit.   (and generally, I try to assume omniscient malware when thinking about security, but not everything has to be super-effective to be part of the interface)

I'm more inclined believe that systems like this do more harm than good, they promote a sense of security in what is a fairly sensitive environment. If the protection is just against casual un-targeted key logging, then I'm not sure of the point, having a password is useless if you don't have the associated Armory wallet binary.

Even more importantly, people who habitually use an onscreen keyboard to type their password (let alone one with a non-standard layout) will ultimately be choosing much weaker passwords as a direct result. This would be detrimental in the situation where malware manages to take the wallet binary but not the password.

Having the feature there implies that it will afford the user security, meaning that people may lapse in believing that will be be an end-all protection from malware, when it's most obviously not.

[jyyst]

I left Armory on for some time and it's crashed:
Log from console:

Code:

[piotrek@localhost BitcoinArmory]$ python2 ArmoryQt.py 
********************************************************************************
Loading Armory Engine:
   Armory Version:       0.89.99.14
   PyBtcWallet  Version: 1.35
Detected Operating system: Linux
   OS Variant            : ('', '', '')
   User home-directory   : /home/piotrek
   Satoshi BTC directory : /home/piotrek/.bitcoin/
   Armory home dir       : /home/piotrek/.armory/
   LevelDB directory     : /home/piotrek/.armory/databases
   Armory settings file  : /home/piotrek/.armory/ArmorySettings.txt
   Armory log file       : /home/piotrek/.armory/armorylog.txt
(WARNING) armoryengine.py:11334 - Overriding not-available message. This should happen 0-5 times
(WARNING) armoryengine.py:11334 - Overriding not-available message. This should happen 0-5 times
(WARNING) armoryengine.py:11334 - Overriding not-available message. This should happen 0-5 times
-INFO  - 1384596030: (BlockUtils.cpp:1582) Set home directory: 
-INFO  - 1384596030: (BlockUtils.cpp:1604) Set blkfile dir: /home/piotrek/.bitcoin/blocks
-INFO  - 1384596030: (BlockUtils.cpp:1614) Set leveldb dir: /home/piotrek/.armory/databases
-INFO  - 1384596030: (BlockUtils.cpp:1570) SetBtcNetworkParams
-INFO  - 1384596030: (BlockUtils.cpp:3563) Executing: doInitialSyncOnLoad
-INFO  - 1384596030: (BlockUtils.cpp:3603) Number of registered addr: 569
-INFO  - 1384596030: (leveldb_wrapper.cpp:127) Opening databases...
-INFO  - 1384596033: (BlockUtils.cpp:1695) Total blk*.dat files:                 53
-INFO  - 1384596033: (BlockUtils.cpp:1713) Current Top block in HEADERS DB:  269794
-INFO  - 1384596033: (BlockUtils.cpp:1714) Current Top block in BLKDATA DB:  269794
-INFO  - 1384596033: (BlockUtils.cpp:1715) Current Applied blocks up to hgt: 0
-INFO  - 1384596037: (BlockUtils.cpp:1816) First unrecognized hash file:       52
-INFO  - 1384596037: (BlockUtils.cpp:1817) Offset of first unrecog block:      34724918
-INFO  - 1384596037: (BlockUtils.cpp:1826) First blkfile not in DB:            52
-INFO  - 1384596037: (BlockUtils.cpp:1827) Location of first block not in DB:  34724918
-INFO  - 1384596037: (BlockUtils.cpp:3645) Fetching stored script histories from DB
-INFO  - 1384596037: (BlockUtils.cpp:3689) Reading all headers and building chain...
-INFO  - 1384596043: (BlockUtils.cpp:3694) Total number of blk*.dat files: 53
-INFO  - 1384596043: (BlockUtils.cpp:3695) Total number of blocks found:   269923
-INFO  - 1384596043: (BlockUtils.cpp:3707) Getting latest blocks from blk*.dat files
-INFO  - 1384596043: (BlockUtils.cpp:3708) Total blockchain bytes: 12,508,360,374
-INFO  - 1384596043: (BlockUtils.cpp:3714) Parsing blockchain file: /home/piotrek/.bitcoin/blocks/blk00052.dat                                                                     
-INFO  - 1384596043: (BlockUtils.cpp:3810) /home/piotrek/.bitcoin/blocks/blk00052.dat is 50,331,648 bytes                                                                          
-INFO  - 1384596077: (BlockUtils.cpp:3728) Processed 129 raw blocks DB (3 seconds)                                                                                                 
-INFO  - 1384596077: (BlockUtils.cpp:3757) Starting scan from block height: 0                                                                                                      
-INFO  - 1384597167: (BlockUtils.cpp:3759) Finished blockchain scan in 683.988 seconds                                                                                             
-INFO  - 1384597179: (BlockUtils.cpp:4245) Added new blocks to memory pool: 1                                                                                                      
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ffa5d46f62e11d67d29baea49bc4c8b3a01099fc58                                                                                    
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ffb1fcf8b21372a97a5af8fa92d798237711c40352                                                                                    
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ffb89a350e116cf1c027bb6ce9415b2e1faac1cb51                                                                                    
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ff8b91abd8dfe1e41c7c7d507c5fe931461d7221f7
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ff033be77ca0159b4e11c7d1e7c1e3ebfd1097a490
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ffc74316acfc9e3893d96cb64706317f5250a91b1a
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ff14e2d06193cdbfd9d0135abb0b78868bb2e99f89
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ffb318afa352aaa8576ca508df4ae25fdc77d9a98f
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ff1758cd4ed1798232ceea844edc4854c843548b2c
(ERROR) armoryengine.py:8527 - Unrecognized scraddr: ffd5a21e648dde5fa02b35fe95e4d94ef76b0a2e1f
-INFO  - 1384598177: (BlockUtils.cpp:4245) Added new blocks to memory pool: 1
New Block:  269924
-INFO  - 1384599172: (BlockUtils.cpp:4245) Added new blocks to memory pool: 1
(ERROR) armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
(ERROR) armoryengine.py:12373 - BDM state is currently: BlockchainReady
(ERROR) armoryengine.py:12374 - Called from: armoryengine.py:12615 (66181266)
(ERROR) armoryengine.py:12375 - BDM currently doing: UpdateWallets (66181266)
(ERROR) armoryengine.py:12376 - Direct traceback
  File "ArmoryQt.py", line 5129, in <module>
    os._exit(QAPP.exec_())
  File "/home/piotrek/Apps/BitcoinArmory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/site-packages/twisted/python/log.py", line 88, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/site-packages/twisted/python/log.py", line 73, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/home/piotrek/Apps/BitcoinArmory/qt4reactor.py", line 102, in _read
    self.reactor._iterate(fromqt=True)
  File "/home/piotrek/Apps/BitcoinArmory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
  File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 824, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4770, in Heartbeat
    TheBDM.updateWalletsAfterScan(wait=True)
  File "/home/piotrek/Apps/BitcoinArmory/armoryengine.py", line 12615, in updateWalletsAfterScan
    return self.waitForOutputIfNecessary(expectOutput, rndID)
  File "/home/piotrek/Apps/BitcoinArmory/armoryengine.py", line 12377, in waitForOutputIfNecessary
    traceback.print_stack()
(ERROR) armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/home/piotrek/Apps/BitcoinArmory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
New Block:  269925
(ERROR) armoryengine.py:12346 - BDM was not ready for your request!  Waited 20 sec.
(ERROR) armoryengine.py:12347 -   getattr   name: scanRegisteredTxForWallet
(ERROR) armoryengine.py:12348 - BDM currently doing: UpdateWallets (66181266)
(ERROR) armoryengine.py:12349 - Waiting for completion: ID= 74594181
(ERROR) armoryengine.py:12350 - Direct traceback
  File "ArmoryQt.py", line 5129, in <module>
    os._exit(QAPP.exec_())
  File "/home/piotrek/Apps/BitcoinArmory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/site-packages/twisted/python/log.py", line 88, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/site-packages/twisted/python/log.py", line 73, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/home/piotrek/Apps/BitcoinArmory/qt4reactor.py", line 102, in _read
    self.reactor._iterate(fromqt=True)
  File "/home/piotrek/Apps/BitcoinArmory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
  File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 824, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4785, in Heartbeat
    self.walletMap[wltID].syncWithBlockchainLite()
  File "/home/piotrek/Apps/BitcoinArmory/armoryengine.py", line 7212, in syncWithBlockchainLite
    TheBDM.scanRegisteredTxForWallet(self.cppWallet, startBlk, wait=True)
  File "/home/piotrek/Apps/BitcoinArmory/armoryengine.py", line 12351, in passthruFunc
    traceback.print_stack()
(ERROR) armoryengine.py:12353 - Traceback:
Traceback (most recent call last):
  File "/home/piotrek/Apps/BitcoinArmory/armoryengine.py", line 12343, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
(ERROR) armoryengine.py:13289 - ErrorOut var over-represented number of errors!
(ERROR) ArmoryQt.py:4824 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 4797, in Heartbeat
    self.createCombinedLedger()
  File "ArmoryQt.py", line 2053, in createCombinedLedger
    self.combinedLedger.sort(key=lambda x: currBlk-x[1].getBlockNum()+1, reverse=not sortDir)
  File "ArmoryQt.py", line 2053, in <lambda>
    self.combinedLedger.sort(key=lambda x: currBlk-x[1].getBlockNum()+1, reverse=not sortDir)
TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
(<type 'exceptions.TypeError'>, TypeError("unsupported operand type(s) for -: 'NoneType' and 'int'",), <traceback object at 0x30e83f8>)
Naruszenie ochrony pamięci (core dumped)

I don't know is this bug but always when i close Armory:

Code:

-INFO  - 1384625610: (BlockUtils.cpp:3999) Saving wallet history for next load
(ERROR) armoryengine.py:13216 - Resetting BDM and all wallets
(WARNING) armoryengine.py:661 - Killing process pid=8379
(ERROR) ArmoryQt.py:4337 - BitcoindNotAvailable: should not happen...
Resetting BlockDataMgr, freeing memory

 

[SimonL]

Here's a bug I've found since the last stable version, I've tried this on 0.89.99.10-beta and 0.89.99.14-beta and I've done a couple rescans too. It seems for me the transactions tab does not populate until it receives a new block after it has finished loading. It pretty much seems to stay like and looks like it is broken until I left it running for a while and then suddenly all the transactions in the window appears, everything else seems to work fine though. This only seemed to happen the first time it was run so, it might be that everything is catching up the first time and it is taking a really long time to reorganise itself. It does report errors in the log though so here they are.

Okay, so I haven't heard of this bug in a long time.  I thought it only happened when you have a corrupt wallet in your list.  If you isolate it better, I got a bounty for you!  What OS?  Can you try making a copy of the ARMORY_HOME_DIR (if you have the space for it), then remove the wallets, and run Armory with " --datadir=/new/directory/path".  Create a single new wallet, then restart and let it sync again.  I need to know if it goes away.  If so, then there's an issue with one of the wallets and I'll dig further.

I'm using Kubuntu 13.04, I'm only using watching only wallets but they are originally generated from a much older version of Armory. When the problem occurred initially in 0.89.90.10-beta I thought maybe the older files were causing problems so I removed everything but the watching only files and used a fresh .armory directory with the newer version 0.89.90.14-beta and the results seemed to be identical, so it is probably something to do with the older watching only wallet files.

I followed your directions, copied the original armory dir, removed everything but the databases directory. Fired up Armory, made a new wallet (no encryption enabled), set the settings to not manage Bitcoin-qt, restarted Armory, databases rebuilt and rescanned, then imported a private key with a tiny balance for testing, closed Armory and removed everything but the databases directory and the new wallet with the imported private key. The balance and transactions appeared immediately after the scan no problem, the priv key had around 90-ish transactions and it looked like it was all there. Re-ran it too just to be sure.

I went back to the original watching wallet files for my original wallets and tried running Armory for each of them separately, all but one loaded the wallet in offline mode. One of my watching wallets now fails to load and has this log output:

Code:

2013-11-17 00:29 (INFO) -- ArmoryQt.py:1633 - loadWalletsAndSettings
2013-11-17 00:29 (INFO) -- ArmoryQt.py:1680 - Loading wallets...
2013-11-17 00:29 (WARNING) -- armoryengine.py:9074 - ***WARNING: creation of backup was interrupted -- fixing
2013-11-17 00:29 (ERROR) -- ArmoryQt.py:1723 - ***WARNING: Wallet could not be loaded: /home/ferret/.armory/armory_35Fijn44X_.watchonly.wallet (skipping)
Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 1695, in loadWalletsAndSettings
    wltLoad = PyBtcWallet().readWalletFile(fpath)
  File "/usr/lib/armory/armoryengine.py", line 8776, in readWalletFile
    nError = self.doWalletFileConsistencyCheck()
  File "/usr/lib/armory/armoryengine.py", line 9075, in doWalletFileConsistencyCheck
    shutil.copy(self.walletPath, walletFileBackup)
  File "/usr/lib/python2.7/shutil.py", line 120, in copy
    copymode(src, dst)
  File "/usr/lib/python2.7/shutil.py", line 91, in copymode
    os.chmod(dst, mode)
OSError: [Errno 1] Operation not permitted: '/home/ferret/.armory/armory_35Fijn44X_.watchonly_backup.wallet'
2013-11-17 00:29 (ERROR) -- Traceback (most recent call last):
  File "/usr/lib/armory/ArmoryQt.py", line 5109, in <module>
    form = ArmoryMainWindow()
  File "/usr/lib/armory/ArmoryQt.py", line 123, in __init__
    self.loadWalletsAndSettings()
  File "/usr/lib/armory/ArmoryQt.py", line 1695, in loadWalletsAndSettings
    wltLoad = PyBtcWallet().readWalletFile(fpath)
  File "/usr/lib/armory/armoryengine.py", line 8776, in readWalletFile
    nError = self.doWalletFileConsistencyCheck()
  File "/usr/lib/armory/armoryengine.py", line 9075, in doWalletFileConsistencyCheck
    shutil.copy(self.walletPath, walletFileBackup)
  File "/usr/lib/python2.7/shutil.py", line 120, in copy
    copymode(src, dst)
  File "/usr/lib/python2.7/shutil.py", line 91, in copymode
    os.chmod(dst, mode)
OSError: [Errno 1] Operation not permitted: '/home/ferret/.armory/armory_35Fijn44X_.watchonly_backup.wallet'

After this I tried using a backup before I started using this new version and it too returns the same error. This is rather strange since the first time I ran it with all the watching wallets in the directory it loaded everything fine and simply had the strange behaviour of not loading the transactions until after a block was processed by Armory after it finished getting started. The watching wallet itself has a lot of imported addresses.

Removing all the files but the databases directory and leaving all the watching only wallet files will still result all of the files being loaded successfully, including the original watching only wallet that failed when loaded on it's own. I've also found that this results in exactly the same behaviour as mentioned in my previous post, none of the transactions in the transaction tab appear on this initial load. So it looks like this particular behaviour can be reproduced. 20 minutes and two blocks later the transactions appeared in full again. There were no errors in the log but here it is:

Code:

2013-11-17 00:54 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 99.8
2013-11-17 00:54 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-17 00:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-17 00:54 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-17 00:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-17 00:54 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2pD6iHKkB
2013-11-17 00:54 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 35Fijn44X
2013-11-17 00:54 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2H5X6XTGs
2013-11-17 00:54 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: CSFC3QFR
2013-11-17 00:54 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2ToSafqhH
2013-11-17 00:54 (INFO) -- ArmoryQt.py:1919 - Current block number: 269945
2013-11-17 00:55 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-17 00:55 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-17 00:55 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-17 00:55 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-17 00:55 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-17 00:55 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-17 00:55 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-17 00:55 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-17 00:55 (INFO) -- ArmoryQt.py:4779 - New Block! : 269946
2013-11-17 00:55 (INFO) -- ArmoryQt.py:4803 - Current block number: 269946
2013-11-17 01:12 (INFO) -- armoryengine.py:10634 - Received new block.  00000000000000047fad31c6ee41e60029ab005b22df147b49192067e33d926e
2013-11-17 01:12 (INFO) -- ArmoryQt.py:4779 - New Block! : 269947
2013-11-17 01:12 (INFO) -- ArmoryQt.py:4803 - Current block number: 269947
2013-11-17 01:17 (INFO) -- ArmoryQt.py:4779 - New Block! : 269948
2013-11-17 01:17 (INFO) -- ArmoryQt.py:4803 - Current block number: 269948

If you need anything else let me know.

[idoB]

Found the following (minor) polishing issues, running on win7 x64:

•    ‘Create Backup Fragments’ dialog: has an http link ‘click here to read more about fragmented backups’ – however, this dialog box is shown only on the offline computer, and therefore this link needs to either point to a local file or not exist at all as newbies might be misled to connect online at the worst possible situation opsec wise.
•   “Bad Backup!” Dialog box (fragmented backups) syntax error: - should be “…then the one you just made” instead of “…then the on you just made”
•   Failed unlock wallet dialog box syntax error: - should be “wallet could not be unlocked” instead of “wallet was not be unlocked”
•   Restore Backup (testing paper backup) dialog box: the ID and Fx fields are prefilled with spaces and they’re not deleted when typing. Need to select all and delete each field actively.

[cp1]

If you specify --datadir, but that directory doesn't exist, Armory will default to appdata/roaming without telling you (except for in the log file).  It would be nice if it would just create this directory for you or at least notify you that you need to create it.

If you run out of space on your drive while building the database it won't throw an error either, it will just sit there at whatever % forever.

Code:

2013-11-16 09:16 (INFO) -- armoryengine.pyc:808 - ************************************************************
2013-11-16 09:16 (INFO) -- armoryengine.pyc:809 - Invoked: C:\Program Files (x86)\Armory-testing\ArmoryQt.exe --satoshi-datadir=I:\bitcoin --datadir=I:\armory
2013-11-16 09:16 (INFO) -- armoryengine.pyc:810 - ************************************************************
2013-11-16 09:16 (INFO) -- armoryengine.pyc:811 - Loading Armory Engine:
2013-11-16 09:16 (INFO) -- armoryengine.pyc:812 -    Armory Version        : 0.89.99.14
2013-11-16 09:16 (INFO) -- armoryengine.pyc:813 -    PyBtcWallet  Version  : 1.35
2013-11-16 09:16 (INFO) -- armoryengine.pyc:814 - Detected Operating system: Windows
2013-11-16 09:16 (INFO) -- armoryengine.pyc:815 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2013-11-16 09:16 (INFO) -- armoryengine.pyc:816 -    User home-directory   : C:\Users\cp1\AppData\Roaming
2013-11-16 09:16 (INFO) -- armoryengine.pyc:817 -    Satoshi BTC directory : I:\bitcoin
2013-11-16 09:16 (INFO) -- armoryengine.pyc:818 -    Armory home dir       : C:\Users\cp1\AppData\Roaming\Armory\
2013-11-16 09:16 (INFO) -- armoryengine.pyc:819 - Detected System Specs    : 
2013-11-16 09:16 (INFO) -- armoryengine.pyc:820 -    Total Available RAM   : 16.00 GB
2013-11-16 09:16 (INFO) -- armoryengine.pyc:821 -    CPU ID string         : AMD64 Family 16 Model 5 Stepping 2, AuthenticAMD
2013-11-16 09:16 (INFO) -- armoryengine.pyc:822 -    Number of CPU cores   : 4 cores
2013-11-16 09:16 (INFO) -- armoryengine.pyc:823 -    System is 64-bit      : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:824 -    Preferred Encoding    : cp1252
2013-11-16 09:16 (INFO) -- armoryengine.pyc:825 - 
2013-11-16 09:16 (INFO) -- armoryengine.pyc:826 - Network Name: Main Network
2013-11-16 09:16 (INFO) -- armoryengine.pyc:827 - Satoshi Port: 8333
2013-11-16 09:16 (INFO) -- armoryengine.pyc:828 - Named options/arguments to armoryengine.py:
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     maxOpenFiles    : 0
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     nettimeout      : 2
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     rescan          : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     leveldbDir      : DEFAULT
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     port            : None
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     interport       : 8223
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     coverageOutputDir: None
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     rebuild         : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     datadir         : I:\armory
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     offline         : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     satoshiPort     : DEFAULT
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     netlog          : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     keypool         : 100
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     coverageInclude : None
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     forceOnline     : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     logDisable      : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     mtdebug         : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     skipVerCheck    : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     settingsPath    : C:\Users\cp1\AppData\Roaming\Armory\ArmorySettings.txt
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     verbosity       : None
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     doDebug         : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     testnet         : False
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     rpcport         : DEFAULT
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     satoshiHome     : I:\bitcoin
2013-11-16 09:16 (INFO) -- armoryengine.pyc:830 -     logFile         : C:\Users\cp1\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2013-11-16 09:16 (INFO) -- armoryengine.pyc:831 - Other arguments:
2013-11-16 09:16 (INFO) -- armoryengine.pyc:834 - ************************************************************
2013-11-16 09:16 (INFO) -- armoryengine.pyc:1040 - C++ block utilities loaded successfully
2013-11-16 09:16 (INFO) -- armoryengine.pyc:13506 - Using the asynchronous/multi-threaded BlockDataManager.
2013-11-16 09:16 (INFO) -- armoryengine.pyc:13507 - Blockchain operations will happen in the background.  
2013-11-16 09:16 (INFO) -- armoryengine.pyc:13508 - Devs: check TheBDM.getBDMState() before asking for data.
2013-11-16 09:16 (INFO) -- armoryengine.pyc:13509 - Registering addresses during rescans will queue them for 
2013-11-16 09:16 (INFO) -- armoryengine.pyc:13510 - inclusion after the current scan is completed.
2013-11-16 09:16 (INFO) -- armoryengine.pyc:11560 - Using settings file: C:\Users\cp1\AppData\Roaming\Armory\ArmorySettings.txt

[ACVentures]

I'm running OSX 10.8, every so often I'll get a dialog saying armory is not in sync because bitcoind/QT is off, however the QT app never quits. My laptop sometimes goes into power save mode, which disables the wifi, I think. Not sure if that has anything to do with it, but I tend to notice it more when waking up my mac. It doesn't just pop up at random while I'm active on it.

here's the closest thing to an error around the time when it gives me the out of sync dialog:

Code:

2013-11-16 12:20 (INFO) -- ArmoryQt.py:4779 - New Block! : 269967
2013-11-16 12:20 (INFO) -- ArmoryQt.py:4803 - Current block number: 269967
2013-11-16 13:43 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-11-16 13:43 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-11-16 13:43 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (66993386)
2013-11-16 13:43 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ZeroConfTxToInsert (1355773)
2013-11-16 13:43 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-11-16 13:43 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/Users/joeschmoe/BitcoinArmory/osx_picobit/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/Queue.py", line 176, in get
Empty
2013-11-16 13:57 (INFO) -- armoryengine.py:10634 - Received new block.  000000000000000345d50a6e4ba96c72eb2809e713748ff94088222a7b6cdf5c
2013-11-16 13:57 (INFO) -- ArmoryQt.py:4779 - New Block! : 269969
2013-11-16 13:57 (INFO) -- ArmoryQt.py:4803 - Current block number: 269969
2013-11-16 13:57 (INFO) -- ArmoryQt.py:4779 - New Block! : 269974
2013-11-16 13:57 (INFO) -- ArmoryQt.py:4803 - Current block number: 269974

usually, armory will fix itself, however this time it's not figuring it out on its own. At the time of posting, QT is telling me the correct block height of 269980... armory is 6 blocks behind and the only way to fix is to quit/relaunch armory. Upon relaunching, armory immediately shows the correct 269980 block height. QT was never stopped in this scenario.

[cp1]

That happens to me too when my computer goes to sleep.  Bitcoin-QT obviously can't download new blocks when your computer is asleep.  And I think it takes longer for bitcoin-qt to wake up then armory or something.

[SimonBelmond]

Very small graphical issue on Windows 7 x64 (probably others as well). When I change my settings in Windows so the everything gets bigger my desktop icons will get bigger. Most programs have an icon which is scaleable without problems. The Armory icon gets very pixly, however. would be nice to have an icon which dies not do that as I quite like the Armory logo.

[devthedev]

Issue with auto scroll up, Windows 8 Pro. 64bit. 8GB RAM. I encountered this bug while using Armory 0.89.99.14-beta / Advanced.. --- Video of the bug below.

http://www.screenr.com/N6QH

Let me know if this helps.

1NjgWevCNQ3XbzAmqr2V3tdTxGwozgYPUT

[128bpm]

OS X 10.7.5, using version from this thread.  App is crashing immediately upon startup, no logfile is written.  I traced this back to a segfault in Python.  Here's the output from gdb:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00000001039ab5eb in qfontForThemeFont ()
#2  0x00000001038ecd93 in qt_mac_update_os_settings ()
#3  0x00000001038eebd5 in qt_init ()
#4  0x000000010394e0c7 in QApplicationPrivate::construct ()
#5  0x000000010394e26b in QApplication::QApplication ()
#6  0x0000000103147237 in init_QApplication ()
#7  0x00000001013c26d8 in sipSimpleWrapper_init ()
#8  0x0000000100062722 in type_call ()
#9  0x000000010000fe25 in PyObject_Call ()
#10 0x00000001000a53c4 in PyEval_EvalFrameEx ()
#11 0x00000001000a1386 in PyEval_EvalCodeEx ()
#12 0x00000001000a0cb6 in PyEval_EvalCode ()
#13 0x00000001000baf27 in PyImport_ExecCodeModuleEx ()
#14 0x00000001000bde2f in load_source_module ()
#15 0x00000001000bea47 in import_submodule ()
#16 0x00000001000be4df in load_next ()
#17 0x00000001000bc3d0 in PyImport_ImportModuleLevel ()
#18 0x000000010009c554 in builtin___import__ ()
#19 0x000000010000fe25 in PyObject_Call ()
#20 0x00000001000a4a73 in PyEval_EvalFrameEx ()
#21 0x00000001000a1386 in PyEval_EvalCodeEx ()
#22 0x00000001000a0cb6 in PyEval_EvalCode ()
#23 0x00000001000baf27 in PyImport_ExecCodeModuleEx ()
#24 0x00000001000bde2f in load_source_module ()
#25 0x00000001000bea47 in import_submodule ()
#26 0x00000001000be4df in load_next ()
#27 0x00000001000bc3d0 in PyImport_ImportModuleLevel ()
#28 0x000000010009c554 in builtin___import__ ()
#29 0x000000010000fe25 in PyObject_Call ()
#30 0x00000001000a4a73 in PyEval_EvalFrameEx ()
#31 0x00000001000a1386 in PyEval_EvalCodeEx ()
#32 0x00000001000a0cb6 in PyEval_EvalCode ()
#33 0x00000001000baf27 in PyImport_ExecCodeModuleEx ()
#34 0x00000001000bde2f in load_source_module ()
#35 0x00000001000bea47 in import_submodule ()
#36 0x00000001000be4df in load_next ()
#37 0x00000001000bc3d0 in PyImport_ImportModuleLevel ()
#38 0x000000010009c554 in builtin___import__ ()
#39 0x000000010000fe25 in PyObject_Call ()
#40 0x00000001000a4a73 in PyEval_EvalFrameEx ()
#41 0x00000001000a1386 in PyEval_EvalCodeEx ()
#42 0x00000001000a0cb6 in PyEval_EvalCode ()
#43 0x00000001000c8351 in PyRun_FileExFlags ()
#44 0x00000001000c7e9e in PyRun_SimpleFileExFlags ()
#45 0x00000001000dcedb in Py_Main ()
#46 0x0000000100000e55 in ?? ()
#47 0x0000000100000d71 in ?? ()
(gdb)

I'm happy to help you test-- let me know what you need.



EDIT: this thread: https://bugreports.qt-project.org/browse/QTBUG-27219?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel

.... seems to suggest that "this problem goes away when adding "-sdk /Developer/SDKs/MacOSX10.6.sdk" to the configure script. "

[SimonBelmond]

I left Armory on for some time and came back some hours later. armory crashed and is now re scanning as it has not shut down properly. I guess I left the computer sometime before 21:00. I came back at around 01:15. So the time in the log makes sense somehow. Why did the log not continue while I was gone? I have no screensaver or anything on. this is a win7 x64 system.

Log from armorylog.txt:

Code:

2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4724 - New blocks added in last 5 sec: 1079936
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4723 - Detected Bitcoin-Qt/bitcoind not synchronized
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4724 - New blocks added in last 5 sec: 809952
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4723 - Detected Bitcoin-Qt/bitcoind not synchronized
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4724 - New blocks added in last 5 sec: 539968
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4723 - Detected Bitcoin-Qt/bitcoind not synchronized
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4724 - New blocks added in last 5 sec: 539968
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4723 - Detected Bitcoin-Qt/bitcoind not synchronized
2013-11-16 21:01 (ERROR) -- ArmoryQt.py:4724 - New blocks added in last 5 sec: 269984
2013-11-17 01:16 (ERROR) -- armoryengine.pyc:12371 - Waiting for BDM output that didn't come after 20s.
2013-11-17 01:16 (ERROR) -- armoryengine.pyc:12372 - BDM state is currently: BlockchainReady
2013-11-17 01:16 (ERROR) -- armoryengine.pyc:12373 - Called from: armoryengine.pyc:12562 (82619579)
2013-11-17 01:16 (ERROR) -- armoryengine.pyc:12374 - BDM currently doing: Passthrough (45966768)
2013-11-17 01:16 (ERROR) -- armoryengine.pyc:12375 - Direct traceback
2013-11-17 01:16 (ERROR) -- armoryengine.pyc:12377 - Traceback:
Traceback (most recent call last):
  File "armoryengine.pyc", line 12367, in waitForOutputIfNecessary
  File "Queue.pyc", line 176, in get
Empty
2013-11-17 01:16 (INFO) -- armoryengine.pyc:805 - 
2013-11-17 01:16 (INFO) -- armoryengine.pyc:806 - 
2013-11-17 01:16 (INFO) -- armoryengine.pyc:807 - 
2013-11-17 01:16 (INFO) -- armoryengine.pyc:808 - ************************************************************
2013-11-17 01:16 (INFO) -- armoryengine.pyc:809 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --offline
2013-11-17 01:16 (INFO) -- armoryengine.pyc:810 - ************************************************************

[jbreher]

OS X 10.7.5. Crashes immediately upon launch. Info from terminal:

Code:

hostname:~ username$ /Applications/Armory.app/Contents/MacOS/Armory
(ERROR) armoryengine.py:795 - Error getting system details:
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine.py", line 793, in <module>
    SystemSpecs = GetSystemDetails()
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine.py", line 785, in GetSystemDetails
    raise OSError, "Can't get system specs in OSX"
OSError: Can't get system specs in OSX
(ERROR) armoryengine.py:796 - Skipping.
/Applications/Armory.app/Contents/MacOS/Armory: line 16: 25592 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py
hostname:~ username$ 

Start of OS X crash report:

Code:

Process:         Python [25592]
Path:            /Applications/Armory.app/Contents/MacOS/Python
Identifier:      com.armory.armory
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  bash [25590]

Date/Time:       2013-11-16 20:10:30.634 -0700
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9

Interval Since Last Report:          147525 sec
Crashes Since Last Report:           3
Per-App Crashes Since Last Report:   3
Anonymous UUID:                      2073DD49-7F33-4177-827A-9A4C34ABF7BA

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

[cp1]

• Restoring paper and digital backups without restarting the app

I restored two wallets after building the database.  The first rescanned fine. The second hung at 0% after the error: 
Traceback (most recent call last):
  File "armoryengine.pyc", line 13409, in run
  File "armoryengine.pyc", line 13051, in __startRescanBlockchain
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'I:\\armory\\blkfiles.txt'

After closing and opening Armory the rescan is going now.

Code:

2013-11-16 18:54 (INFO) -- ArmoryQt.py:2737 - Copying imported wallet to: I:\armory\armory_hx7YPBfV_.wallet
2013-11-16 18:54 (INFO) -- ArmoryQt.py:2805 - Raw import successful.
2013-11-16 18:54 (INFO) -- ArmoryQt.py:4779 - New Block! : 270018
2013-11-16 18:54 (INFO) -- ArmoryQt.py:4803 - Current block number: 270018
2013-11-16 18:54 (INFO) -- ArmoryQt.py:2864 - User requested rescan after wallet restore
2013-11-16 18:54 (INFO) -- ArmoryQt.py:1854 - Starting blockchain rescan...
2013-11-16 18:54 (INFO) -- armoryengine.pyc:12587 - Blockchain rescan requested
2013-11-16 18:54 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 18:54 (INFO) -- armoryengine.pyc:13061 - Rescan requested, and very large scan is necessary
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 18:54 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 18:54 (INFO) -- ArmoryQt.py:2310 - addWalletToApplication
2013-11-16 18:54 (INFO) -- ArmoryQt.py:2884 - Import Complete!
2013-11-16 18:54 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 18:54 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 18:54 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.2
2013-11-16 18:54 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.5
2013-11-16 18:54 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.6
2013-11-16 18:55 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.9
2013-11-16 18:55 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 1.0
2013-11-16 18:55 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 1.1
2013-11-16 18:55 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 1.2
2013-11-16 18:55 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 1.3

=snip=

2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 87.7
2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 88.1
2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 88.5
2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 88.9
2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 89.2
2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 89.6
2013-11-16 19:16 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 90.0
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 90.4
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 90.8
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 91.2
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 91.6
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 92.1
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 92.5
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 92.9
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 93.3
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 93.6
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 94.0
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 94.4
2013-11-16 19:17 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 94.7
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 95.1
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 95.5
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 95.8
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 96.2
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 96.6
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 97.0
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 97.4
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 97.8
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 98.1
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 98.6
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 98.9
2013-11-16 19:18 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 99.3
2013-11-16 19:19 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 99.6
2013-11-16 19:19 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 19:19 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 19:19 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 19:19 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 19:20 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-16 19:20 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: hx7YPBfV
2013-11-16 19:20 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2tWBqbSmu
2013-11-16 19:20 (INFO) -- ArmoryQt.py:1919 - Current block number: 270047
2013-11-16 19:20 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-16 19:20 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-16 19:20 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-16 19:25 (INFO) -- ArmoryQt.py:2737 - Copying imported wallet to: I:\armory\armory_QmiL2AUf_.wallet
2013-11-16 19:25 (INFO) -- ArmoryQt.py:2805 - Raw import successful.
2013-11-16 19:25 (INFO) -- ArmoryQt.py:2864 - User requested rescan after wallet restore
2013-11-16 19:25 (INFO) -- ArmoryQt.py:1854 - Starting blockchain rescan...
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12587 - Blockchain rescan requested
2013-11-16 19:25 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 19:25 (ERROR) -- armoryengine.pyc:13471 - Error processing BDM input
2013-11-16 19:25 (ERROR) -- armoryengine.pyc:13472 - Received inputTuple: RescanRequested [9, 57461814, False, 'AsNeeded']
2013-11-16 19:25 (ERROR) -- armoryengine.pyc:13473 - Error processing ID (57461814)
2013-11-16 19:25 (ERROR) -- armoryengine.pyc:13474 - ERROR:
Traceback (most recent call last):
  File "armoryengine.pyc", line 13409, in run
  File "armoryengine.pyc", line 13051, in __startRescanBlockchain
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'I:\\armory\\blkfiles.txt'
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 19:25 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 19:25 (INFO) -- ArmoryQt.py:2310 - addWalletToApplication
2013-11-16 19:25 (INFO) -- ArmoryQt.py:2884 - Import Complete!
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 19:25 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:25 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:26 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:27 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:28 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:29 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.0
2013-11-16 19:30 (INFO) -- ArmoryQt.py:4977 - BDM state is scanning -- force shutdown BDM
2013-11-16 19:30 (INFO) -- armoryengine.pyc:11262 - Called stopBitcoind
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13434 - Shutdown Requested
2013-11-16 19:30 (INFO) -- armoryengine.pyc:11264 - ...but bitcoind is not running, to be able to stop
2013-11-16 19:30 (INFO) -- ArmoryQt.py:5006 - Attempting to close the main window!
2013-11-16 19:30 (ERROR) -- armoryengine.pyc:13215 - Resetting BDM and all wallets
2013-11-16 19:30 (INFO) -- ArmoryQt.py:5117 - Resetting BlockDataMgr, freeing memory
2013-11-16 19:30 (INFO) -- armoryengine.pyc:805 - 
2013-11-16 19:30 (INFO) -- armoryengine.pyc:806 - 
2013-11-16 19:30 (INFO) -- armoryengine.pyc:807 - 
2013-11-16 19:30 (INFO) -- armoryengine.pyc:808 - ************************************************************
2013-11-16 19:30 (INFO) -- armoryengine.pyc:809 - Invoked: C:\Program Files (x86)\Armory-testing\ArmoryQt.exe --satoshi-datadir=I:\bitcoin --datadir=I:\armory
2013-11-16 19:30 (INFO) -- armoryengine.pyc:810 - ************************************************************
2013-11-16 19:30 (INFO) -- armoryengine.pyc:811 - Loading Armory Engine:
2013-11-16 19:30 (INFO) -- armoryengine.pyc:812 -    Armory Version        : 0.89.99.14
2013-11-16 19:30 (INFO) -- armoryengine.pyc:813 -    PyBtcWallet  Version  : 1.35
2013-11-16 19:30 (INFO) -- armoryengine.pyc:814 - Detected Operating system: Windows
2013-11-16 19:30 (INFO) -- armoryengine.pyc:815 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2013-11-16 19:30 (INFO) -- armoryengine.pyc:816 -    User home-directory   : C:\Users\cp1\AppData\Roaming
2013-11-16 19:30 (INFO) -- armoryengine.pyc:817 -    Satoshi BTC directory : I:\bitcoin
2013-11-16 19:30 (INFO) -- armoryengine.pyc:818 -    Armory home dir       : I:\armory
2013-11-16 19:30 (INFO) -- armoryengine.pyc:819 - Detected System Specs    : 
2013-11-16 19:30 (INFO) -- armoryengine.pyc:820 -    Total Available RAM   : 16.00 GB
2013-11-16 19:30 (INFO) -- armoryengine.pyc:821 -    CPU ID string         : AMD64 Family 16 Model 5 Stepping 2, AuthenticAMD
2013-11-16 19:30 (INFO) -- armoryengine.pyc:822 -    Number of CPU cores   : 4 cores
2013-11-16 19:30 (INFO) -- armoryengine.pyc:823 -    System is 64-bit      : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:824 -    Preferred Encoding    : cp1252
2013-11-16 19:30 (INFO) -- armoryengine.pyc:825 - 
2013-11-16 19:30 (INFO) -- armoryengine.pyc:826 - Network Name: Main Network
2013-11-16 19:30 (INFO) -- armoryengine.pyc:827 - Satoshi Port: 8333
2013-11-16 19:30 (INFO) -- armoryengine.pyc:828 - Named options/arguments to armoryengine.py:
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     maxOpenFiles    : 0
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     nettimeout      : 2
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     rescan          : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     leveldbDir      : DEFAULT
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     port            : None
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     interport       : 8223
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     coverageOutputDir: None
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     rebuild         : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     datadir         : I:\armory
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     offline         : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     satoshiPort     : DEFAULT
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     netlog          : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     keypool         : 100
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     coverageInclude : None
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     forceOnline     : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     logDisable      : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     mtdebug         : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     skipVerCheck    : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     settingsPath    : I:\armory\ArmorySettings.txt
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     verbosity       : None
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     doDebug         : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     testnet         : False
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     rpcport         : DEFAULT
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     satoshiHome     : I:\bitcoin
2013-11-16 19:30 (INFO) -- armoryengine.pyc:830 -     logFile         : I:\armory\ArmoryQt.exe.log.txt
2013-11-16 19:30 (INFO) -- armoryengine.pyc:831 - Other arguments:
2013-11-16 19:30 (INFO) -- armoryengine.pyc:834 - ************************************************************
2013-11-16 19:30 (INFO) -- armoryengine.pyc:1040 - C++ block utilities loaded successfully
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13506 - Using the asynchronous/multi-threaded BlockDataManager.
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13507 - Blockchain operations will happen in the background.  
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13508 - Devs: check TheBDM.getBDMState() before asking for data.
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13509 - Registering addresses during rescans will queue them for 
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13510 - inclusion after the current scan is completed.
2013-11-16 19:30 (INFO) -- armoryengine.pyc:11560 - Using settings file: I:\armory\ArmorySettings.txt
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1633 - loadWalletsAndSettings
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1680 - Loading wallets...
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1728 - Number of wallets read in: 3
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1733 -    Wallet (hx7YPBfV):    "Tips                            "   (Encrypted)
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1733 -    Wallet (QmiL2AUf):    "Mining                          "   (Encrypted)
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1733 -    Wallet (2tWBqbSmu):   "Primary Wallet (Watch)          "   (No Encryption)
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1311 - Setting up networking...
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1364 - Internet connection is Available: True
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1365 - Bitcoin-Qt/bitcoind is Available: 8333
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1366 - The first blk*.dat was Available: True
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1367 - Online mode currently possible:   True
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1428 - loadBlockchainIfNecessary
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1474 - Setting netmode: 1
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12525 - Setting online mode: True (wait=False)
2013-11-16 19:30 (INFO) -- armoryengine.pyc:13446 - Go online requested
2013-11-16 19:30 (INFO) -- armoryengine.pyc:12967 - Called __startLoadBlockchain()
2013-11-16 19:30 (INFO) -- ArmoryQt.py:877 - setupUriRegistration
2013-11-16 19:30 (WARNING) -- ArmoryQt.py:925 - running from: C:\Program Files (x86)\Armory-testing\ArmoryQt.exe, key: "C:\Program Files (x86)\Armory-testing\ArmoryQt.exe" %1
2013-11-16 19:30 (INFO) -- ArmoryQt.py:935 - Armory already registered for current user.  Done!
2013-11-16 19:30 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 19:30 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 19:30 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 19:30 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 19:30 (INFO) -- ArmoryQt.py:532 - Usermode: Advanced
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1144 - Changing usermode:
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1145 -    From: Advanced
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1153 -      To: Advanced
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10488 - Connection initiated.  Start handshake
2013-11-16 19:30 (INFO) -- ArmoryQt.py:4473 - Dashboard switched to "Scanning" mode
2013-11-16 19:30 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2013-11-16 19:30 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2013-11-16 19:30 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Scanning"
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10577 - Received version message from peer:
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10578 -    Version:     70001
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10579 -    SubVersion:  /Satoshi:0.8.5/
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10580 -    TimeStamp:   1384659153
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10581 -    StartHeight: 270048
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10759 - Handshake finished, connection open!
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10881 - Signature on signed data block is GOOD!
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1283 - Latest versions:
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1284 -    Satoshi: 0.8.1
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1285 -     Armory: 0.88
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1294 - You are running the latest version!
2013-11-16 19:30 (INFO) -- armoryengine.pyc:10881 - Signature on signed data block is GOOD!
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1283 - Latest versions:
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1284 -    Satoshi: 0.8.1
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1285 -     Armory: 0.88
2013-11-16 19:30 (INFO) -- ArmoryQt.py:1294 - You are running the latest version!
2013-11-16 19:30 (INFO) -- ArmoryQt.py:4565 - Satoshi Version: Curr: 805000, Latest: 801000
2013-11-16 19:31 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.5
2013-11-16 19:31 (INFO) -- armoryengine.pyc:12478 - Reading blockchain, pct complete: 0.8

[flipperfish]

I found two minor usability/gui bugs:

• In the "Send Bitcoins"-Dialog, if I send Bitcoins from one wallet to another wallet, the target wallet is shown in blue under the target address. However, the target wallet in blue is only shown for the first five recipients.
• In the "Addressbook"-Dialog, right after opening the dialog, the tableheader indicates, that the list should be sorted by address-number (#), which it is not. After clicking the corresponding tableheader (the #), the sorting is correct.

Tested on Windows 7 x64, Armory 0.89.99.14-beta / Expert.

[picobit]

OS X 10.9 Users:

Please disable App Nap for Bitcoin-Qt and Armory, otherwise they go to sleep as soon as their windows are covered.  In particular, if Bitcoin-Qt is sleeping, Armory will not work properly.

Right-click on the app, select Get Info and disable App Nap.  App Nap was introduced in OSX 10.9, so it should not be a problem on older OSX'es.

[SimonBelmond]

One more feature request: I would like that armory keeps the latest synced data available to be viewed before it is back online when starting the next time. Shown in gray or something. that way you could already plan on what you are going to to from what wallets etc. before Armory is online. This can be very handy if you haven't synced for a long time but you are pretty sure balances did not change. Not high priority but I just wanted to mention that.

[Super-Magician]

I haven't seen this reported yet but it's been present for at least a few versions of Armory.

When a new tx gets to 1 confirmation, the tx list view will update, but the tx info will still say that the tx is Not in the blockchain yet and have no confirmation count. I believe the block number is shown correctly after 2 confirmations, though. If it matters, I'm using Expert mode.

[redphlegm]

Mac OSX 10.8.5 Crash

Code:

Process:         Python [58678]
Path:            /Applications/Armory.app/Contents/MacOS/Python
Identifier:      com.armory.armory
Version:         0.89.99.14-beta
Code Type:       X86-64 (Native)
Parent Process:  bash [58675]
User ID:         501

OS Version:      Mac OS X 10.8.5 (12F45)
Report Version:  10

Interval Since Last Report:          1710132 sec
Crashes Since Last Report:           2
Per-App Crashes Since Last Report:   2

Crashed Thread:  2

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000017851d9f5

VM Regions Near 0x17851d9f5:
    mapped file            00000001720ea000-00000001722ef000 [ 2068K] r--/r-x SM=PRV  /Users/USER/Library/Application Support/Armory/*/*.sst
--> 
    CG shared images       00000001c0001000-00000001c0009000 [   32K] rw-/rw- SM=SHM  

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff95ffe322 __select + 10
1   time.so                       	0x00000001011399af time_sleep + 143
2   org.python.python             	0x00000001000a3320 PyEval_EvalFrameEx + 7712
3   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
4   org.python.python             	0x00000001000a8246 fast_function + 294
5   org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
6   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
7   org.python.python             	0x00000001000a8246 fast_function + 294
8   org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
9   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
10  org.python.python             	0x00000001000a8246 fast_function + 294
11  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
12  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
13  org.python.python             	0x00000001000a8246 fast_function + 294
14  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
15  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
16  org.python.python             	0x0000000100033556 function_call + 342
17  org.python.python             	0x000000010000fe25 PyObject_Call + 101
18  org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
19  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
20  org.python.python             	0x00000001000a8246 fast_function + 294
21  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
22  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
23  org.python.python             	0x0000000100033556 function_call + 342
24  org.python.python             	0x000000010000fe25 PyObject_Call + 101
25  org.python.python             	0x000000010001be46 instancemethod_call + 166
26  org.python.python             	0x000000010000fe25 PyObject_Call + 101
27  org.python.python             	0x00000001000a79ad PyEval_CallObjectWithKeywords + 93
28  sip.so                        	0x000000010122f43c sip_api_invoke_slot + 401
29  QtCore.so                     	0x0000000101707709 PyQtProxy::invokeSlot(qpycore_slot const&, void**) + 169
30  QtCore.so                     	0x00000001017075b0 PyQtProxy::unislot(void**) + 160
31  QtCore.so                     	0x00000001017074fe PyQtProxy::qt_metacall(QMetaObject::Call, int, void**) + 110
32  QtCore                        	0x000000010198299e QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1912
33  QtCore.so                     	0x00000001016d68d2 sipQTimer::timerEvent(QTimerEvent*) + 98
34  QtCore                        	0x000000010197ef46 QObject::event(QEvent*) + 48
35  QtCore.so                     	0x00000001016d6942 sipQTimer::event(QEvent*) + 98
36  QtGui                         	0x0000000104852488 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 198
37  QtGui                         	0x0000000104854aa7 QApplication::notify(QObject*, QEvent*) + 5733
38  QtGui.so                      	0x0000000104046dd9 sipQApplication::notify(QObject*, QEvent*) + 121
39  QtCore                        	0x000000010196f639 QCoreApplication::notifyInternal(QObject*, QEvent*) + 101
40  QtGui                         	0x0000000104855371 qt_sendSpontaneousEvent(QObject*, QEvent*) + 44
41  QtGui                         	0x000000010480f44b QEventDispatcherMacPrivate::activateTimer(__CFRunLoopTimer*, void*) + 125
42  com.apple.CoreFoundation      	0x00007fff97b11804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
43  com.apple.CoreFoundation      	0x00007fff97b1131d __CFRunLoopDoTimer + 557
44  com.apple.CoreFoundation      	0x00007fff97af6ad9 __CFRunLoopRun + 1529
45  com.apple.CoreFoundation      	0x00007fff97af60e2 CFRunLoopRunSpecific + 290
46  com.apple.HIToolbox           	0x00007fff971eaeb4 RunCurrentEventLoopInMode + 209
47  com.apple.HIToolbox           	0x00007fff971eab94 ReceiveNextEventCommon + 166
48  com.apple.HIToolbox           	0x00007fff971eaae3 BlockUntilNextEventMatchingListInMode + 62
49  com.apple.AppKit              	0x00007fff98e43533 _DPSNextEvent + 685
50  com.apple.AppKit              	0x00007fff98e42df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
51  com.apple.AppKit              	0x00007fff98e3a1a3 -[NSApplication run] + 517
52  QtGui                         	0x000000010480fe01 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 461
53  QtCore                        	0x000000010196cd89 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 79
54  QtCore                        	0x000000010196cee7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 341
55  QtCore                        	0x000000010196fa6b QCoreApplication::exec() + 199
56  QtGui.so                      	0x0000000104048330 meth_QApplication_exec_ + 80
57  org.python.python             	0x00000001000a3320 PyEval_EvalFrameEx + 7712
58  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
59  org.python.python             	0x00000001000a0cb6 PyEval_EvalCode + 54
60  org.python.python             	0x00000001000c8351 PyRun_FileExFlags + 161
61  org.python.python             	0x00000001000c7e9e PyRun_SimpleFileExFlags + 718
62  org.python.python             	0x00000001000dcedb Py_Main + 3307
63  Python                        	0x0000000100000e55 0x100000000 + 3669
64  Python                        	0x0000000100000d71 0x100000000 + 3441

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x00007fff95ffed16 kevent + 10
1   libdispatch.dylib             	0x00007fff8db8adea _dispatch_mgr_invoke + 883
2   libdispatch.dylib             	0x00007fff8db8a9ee _dispatch_mgr_thread + 54

Thread 2 Crashed:
0   _CppBlockUtils.so             	0x0000000107907334 BtcUtils::readVarInt(unsigned char const*, unsigned int*) + 4
1   _CppBlockUtils.so             	0x000000010793da6a BtcUtils::TxCalcLength(unsigned char const*, std::__1::vector<unsigned int, std::__1::allocator<unsigned int> >*, std::__1::vector<unsigned int, std::__1::allocator<unsigned int> >*) + 490
2   _CppBlockUtils.so             	0x0000000107938121 Tx::unserialize(unsigned char const*) + 33
3   _CppBlockUtils.so             	0x0000000107938308 Tx::unserialize(BinaryRefReader&) + 24
4   _CppBlockUtils.so             	0x0000000107933e5f Tx::Tx(BinaryRefReader&) + 191
5   _CppBlockUtils.so             	0x00000001079232d3 StoredHeader::unserializeFullBlock(BinaryRefReader, bool, bool) + 547
6   _CppBlockUtils.so             	0x000000010795fd55 BlockDataManager_LevelDB::addRawBlockToDB(BinaryRefReader&) + 261
7   _CppBlockUtils.so             	0x0000000107960936 BlockDataManager_LevelDB::addNewBlockData(BinaryRefReader&, unsigned int, unsigned int, unsigned int) + 1478
8   _CppBlockUtils.so             	0x000000010795ecb7 BlockDataManager_LevelDB::readBlkFileUpdate() + 3031
9   _CppBlockUtils.so             	0x0000000107b1e5fe _wrap_BlockDataManager_LevelDB_readBlkFileUpdate + 110
10  org.python.python             	0x00000001000a3320 PyEval_EvalFrameEx + 7712
11  org.python.python             	0x00000001000a81e2 fast_function + 194
12  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
13  org.python.python             	0x00000001000a81e2 fast_function + 194
14  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
15  org.python.python             	0x00000001000a81e2 fast_function + 194
16  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
17  org.python.python             	0x00000001000a81e2 fast_function + 194
18  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
19  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
20  org.python.python             	0x0000000100033556 function_call + 342
21  org.python.python             	0x000000010000fe25 PyObject_Call + 101
22  org.python.python             	0x000000010001be46 instancemethod_call + 166
23  org.python.python             	0x000000010000fe25 PyObject_Call + 101
24  org.python.python             	0x00000001000a79ad PyEval_CallObjectWithKeywords + 93
25  org.python.python             	0x00000001000def26 t_bootstrap + 70
26  libsystem_c.dylib             	0x00007fff97fdf772 _pthread_start + 327
27  libsystem_c.dylib             	0x00007fff97fcc1a1 thread_start + 13

Thread 3:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        	0x00007fff95ffe322 __select + 10
1   com.apple.CoreFoundation      	0x00007fff97b35f46 __CFSocketManager + 1302
2   libsystem_c.dylib             	0x00007fff97fdf772 _pthread_start + 327
3   libsystem_c.dylib             	0x00007fff97fcc1a1 thread_start + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff95ffe0fa __psynch_cvwait + 10
1   libsystem_c.dylib             	0x00007fff97fe3fb9 _pthread_cond_wait + 869
2   _CppBlockUtils.so             	0x0000000107a678a7 leveldb::(anonymous namespace)::PosixEnv::BGThreadWrapper(void*) + 71
3   libsystem_c.dylib             	0x00007fff97fdf772 _pthread_start + 327
4   libsystem_c.dylib             	0x00007fff97fcc1a1 thread_start + 13

Thread 2 crashed with X86 Thread State (64-bit):
  rax: 0x0000000101bc0862  rbx: 0x00000000000000d3  rcx: 0x000000007695d18b  rdx: 0x00000000000041d0
  rdi: 0x000000017851d9f5  rsi: 0x00000001084ff0d4  rbp: 0x00000001084ff0a0  rsp: 0x00000001084ff0a0
   r8: 0x0000000000000037   r9: 0x000000000000000f  r10: 0x0000000000000000  r11: 0x000000012403e570
  r12: 0x00000000000000de  r13: 0x000000000000001a  r14: 0x00000001084ff3d0  r15: 0x00000001084ff0d4
  rip: 0x0000000107907334  rfl: 0x0000000000010202  cr2: 0x000000017851d9f5
Logical CPU: 2

Binary Images:
       0x100000000 -        0x100000fff +Python (???) <7391C337-F313-3DC3-8858-F4D98576338F> /Applications/Armory.app/Contents/MacOS/Python
       0x100003000 -        0x100138fff +org.python.python (2.7.5, [c] 2004-2013 Python Software Foundation. - 2.7.5) <103FEDE5-3388-3C57-BE91-77B2A5BD334E> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/Python
       0x1002ea000 -        0x1002ebfff +_hashlib.so (???) <66995330-32CB-3BF7-B7BD-7DC6F0D5F010> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_hashlib.so
       0x1002f1000 -        0x1002f6ff7 +math.so (???) <05B6A5E0-C126-32A5-8D5C-02E9DC18D040> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/math.so
       0x1010c0000 -        0x1010c3ff7 +strop.so (???) <A8A3031A-3F57-3502-8852-1E4D4BE9C5C1> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/strop.so
       0x1010c8000 -        0x1010d1fff +_socket.so (???) <BEEBF58D-1EEB-3327-8225-7826F1DCA131> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_socket.so
       0x1010dd000 -        0x1010defff +_functools.so (???) <714F7066-2337-307F-814D-8BB324FC58E4> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_functools.so
       0x1010e1000 -        0x1010e5fff +_ssl.so (???) <4A8EBFED-C759-3121-AE17-E1D2BDA066E1> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_ssl.so
       0x1010ea000 -        0x1010ebff7 +cStringIO.so (???) <DAA613C0-EB6F-3CEA-B643-638DBC825EF9> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cStringIO.so
       0x1010f0000 -        0x1010f3ff7 +select.so (???) <91879F38-A462-31CE-84E9-6C9A38C15FB9> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/select.so
       0x1010f8000 -        0x1010f9fff +fcntl.so (???) <EA903793-FD87-3629-ABB0-AC91568532A0> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/fcntl.so
       0x1010fc000 -        0x1010fcff7 +_psutil_posix.so (???) <7837F31B-7449-3475-A592-CF70D25E38CB> /Users/USER/*/_psutil_posix.so
       0x10112e000 -        0x101130ff7 +binascii.so (???) <0E85E810-30D8-3291-BA3B-C09AAED95CA4> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/binascii.so
       0x101134000 -        0x101135fff +_random.so (???) <DDB8196F-D9AD-3F53-ACC9-B423D286AA6C> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_random.so
       0x101138000 -        0x10113aff7 +time.so (???) <AA4C9201-E5E5-3918-8B0A-35F3DF8526B8> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/time.so
       0x10113f000 -        0x101142fff +_collections.so (???) <2995AA80-2ACF-3A43-883C-4740A6EC4252> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_collections.so
       0x101148000 -        0x10114bfff +operator.so (???) <C27445B2-EA33-3929-911A-3E550B32A5CF> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/operator.so
       0x101152000 -        0x101158fff +itertools.so (???) <523081B5-2491-3FE1-96FF-A2CA3B9A8736> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/itertools.so
       0x101163000 -        0x101164ff7 +_heapq.so (???) <B0F48B0B-2F5D-38AD-936A-535EE8DB648F> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_heapq.so
       0x101168000 -        0x101168fff +grp.so (???) <6938ADFC-882E-3FA2-9AE1-4E8BC7DE0422> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/grp.so
       0x10116b000 -        0x10116fff7 +_struct.so (???) <E5CD2D4A-F7B9-36D6-A565-89796ECA3022> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_struct.so
       0x101176000 -        0x101179fff +zlib.so (???) <14D6DE90-0442-3E3A-8C70-8D86E7912A34> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/zlib.so
       0x10117e000 -        0x101190ff7 +_io.so (???) <16EA57D4-FB53-3056-9C4B-A335843A47A2> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_io.so
       0x1011a7000 -        0x1011b3ff7 +parser.so (???) <6552B078-C32B-3005-B2DC-887AAAF3BF10> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/parser.so
       0x1011ba000 -        0x1011bbfff +_locale.so (???) <BF96445B-0F0E-36ED-9C75-E0F36BC23425> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_locale.so
       0x101200000 -        0x10120dfff +datetime.so (???) <ADCF6897-789D-37A3-9C15-D7EB0E417482> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/datetime.so
       0x101219000 -        0x10121eff7 +_psutil_osx.so (???) <45C430C1-AA84-32C5-A321-0326C3531C75> /Users/USER/*/_psutil_osx.so
       0x101223000 -        0x101232ff7 +sip.so (0) <87A4CE0D-66A8-3818-B1DD-628D3D5BAE8A> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/sip.so
       0x10123b000 -        0x10123bff7 +_scproxy.so (???) <342235F5-0C31-3639-A855-D8D38B8F0789> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_scproxy.so
       0x1013c0000 -        0x1013e9ff7 +pyexpat.so (???) <F1AEDE79-6FAA-34BE-9CD8-91436EC94BE6> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/pyexpat.so
       0x101600000 -        0x101769ff7 +QtCore.so (0) <70D24F05-CA51-37B2-847C-369EF4662889> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtCore.so
       0x101875000 -        0x101adcff7 +QtCore (4.8.5) <0906F7C6-CD49-378D-9787-A05C39A15F83> /Applications/Armory.app/Contents/Dependencies/qt/4.8.5/lib/QtCore.framework/Versions/4/QtCore
       0x101bf3000 -        0x101bf6ff7 +_multiprocessing.so (???) <FCEA451B-B413-33CC-B581-A4C923CCE1D9> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_multiprocessing.so
       0x101f34000 -        0x101f41ff7 +cPickle.so (???) <0F160548-0FFD-3940-9D58-0A0E369DBCE4> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cPickle.so
       0x101fc9000 -        0x101fccfff +_zope_interface_coptimizations.so (???) <F49E6A73-1AC7-38EB-B65F-E1F98755EABE> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/zope.interface-4.0.5-py2.7-macosx-10.4-x86_64.egg/zope/interface/_zope_interface_coptimizations.so
       0x101fd2000 -        0x101fd6ff7 +_json.so (???) <E79ADB24-8B7E-36CD-BCFB-8C9505EA2D9F> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_json.so
       0x101fdb000 -        0x101fe0ff7 +array.so (???) <8D7524E9-02E1-35EA-8B73-866E6E2A44E5> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/array.so
       0x104000000 -        0x104467ff7 +QtGui.so (0) <175A92D4-F076-3EE8-9A57-B88E0C510C18> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtGui.so
       0x1047db000 -        0x105042ff7 +QtGui (4.8.5) <232BB82A-03AD-394E-8515-65389C77FA9F> /Applications/Armory.app/Contents/Dependencies/qt/4.8.5/lib/QtGui.framework/Versions/4/QtGui
       0x107901000 -        0x107c6eff7 +_CppBlockUtils.so (0) <9DFEB5A6-5E9A-32BE-BB59-B1491B855108> /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so
       0x107fed000 -        0x107ff6fe7  libcldcpuengine.dylib (2.2.16) <DB9678F6-7D50-384A-A961-6109B61D1607> /System/Library/Frameworks/OpenCL.framework/Libraries/libcldcpuengine.dylib
       0x108586000 -        0x1085aaff7  com.apple.security.csparser (3.0 - 55179.13) <B85553DE-708C-3C20-93D5-70DC80068CE3> /System/Library/Frameworks/Security.framework/PlugIns/csparser.bundle/Contents/MacOS/csparser
       0x1085e6000 -        0x1085e6ffb +cl_kernels (???) <6F067772-BC89-4B32-B52D-C17744BAC51C> cl_kernels
       0x109a25000 -        0x109adeff7  ColorSyncDeprecated.dylib (400) <7CE58F6E-D2C8-39FB-8EE0-28CC6EC6D04F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/Resources/ColorSyncDeprecated.dylib
       0x10aed9000 -        0x10aedafff +Qt.so (0) <C02279D6-2F82-323A-BE48-649E6E2108B1> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/Qt.so
       0x10aedd000 -        0x10aedefff +termios.so (???) <350F3281-B775-3E63-A640-7E69D44D1433> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/termios.so
       0x10d80e000 -        0x10d83cfff +QtXml.so (0) <88794FB6-7487-3D3A-AA37-A21080BCC211> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtXml.so
       0x10d863000 -        0x10d897fff +QtXml (4.8.5) <23911DC8-0AFA-33E4-B760-E0B512BA3C2D> /Applications/Armory.app/Contents/Dependencies/qt/4.8.5/lib/QtXml.framework/Versions/4/QtXml
       0x10ebff000 -        0x10ebffff7 +_bisect.so (???) <67C5854D-986D-39CB-8EBD-96571999BCE7> /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/_bisect.so
       0x10fb42000 -        0x10fbdcff7  unorm8_bgra.dylib (2.2.16) <5D62BED8-DF5D-3C51-94B4-57368FF10DDB> /System/Library/Frameworks/OpenCL.framework/Libraries/ImageFormats/unorm8_bgra.dylib
    0x7fff6a590000 -     0x7fff6a5c493f  dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
    0x7fff8ceca000 -     0x7fff8ceceff7  com.apple.CommonPanels (1.2.5 - 94) <AAC003DE-2D6E-38B7-B66B-1F3DA91E7245> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff8cecf000 -     0x7fff8ced1fff  com.apple.securityhi (4.0 - 55002) <34E45C60-DC7E-3FCC-A1ED-EBF48B77C559> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff8ced2000 -     0x7fff8ced8ff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
    0x7fff8ced9000 -     0x7fff8cf1cff7  com.apple.bom (12.0 - 192) <0BF1F2D2-3648-36B7-BE4B-551A0173209B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x7fff8cf1d000 -     0x7fff8d152ff7  com.apple.CoreData (106.1 - 407.7) <A676E1A4-2144-376B-92B8-B450DD1D78E5> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff8d153000 -     0x7fff8d210ff7  com.apple.ColorSync (4.8.0 - 4.8.0) <6CE333AE-EDDB-3768-9598-9DB38041DC55> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff8d222000 -     0x7fff8d25ffef  libGLImage.dylib (8.10.1) <91E31B9B-4141-36D5-ABDC-20F1D6D1D0CF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff8d521000 -     0x7fff8d523ff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
    0x7fff8d535000 -     0x7fff8d547ff7  libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
    0x7fff8d549000 -     0x7fff8d54aff7  libSystem.B.dylib (169.3) <365477AB-D641-389D-B8F4-A1FAE9657EEE> /usr/lib/libSystem.B.dylib
    0x7fff8d700000 -     0x7fff8d768fff  libvDSP.dylib (380.10) <3CA154A3-1BE5-3CF4-BE48-F0A719A963BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff8d769000 -     0x7fff8d7d2fff  libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
    0x7fff8d7d3000 -     0x7fff8d7f8ff7  libc++abi.dylib (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /usr/lib/libc++abi.dylib
    0x7fff8d7f9000 -     0x7fff8d904fff  libFontParser.dylib (84.6) <96C42E49-79A6-3475-B5E4-6A782599A6DA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff8d93b000 -     0x7fff8d950fff  com.apple.ImageCapture (8.0 - 8.0) <17A45CE6-7DA3-36A5-B7EF-72BC136981AE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff8d951000 -     0x7fff8da6afff  com.apple.ImageIO.framework (3.2.2 - 851) <6552C673-9F29-3B31-A12E-C4391A950965> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff8da6b000 -     0x7fff8da71fff  libCGXCoreImage.A.dylib (333.1) <FBAAF933-1798-3E53-B071-88C930D6BDEF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
    0x7fff8da72000 -     0x7fff8da94ff7  com.apple.Kerberos (2.0 - 1) <C49B8820-34ED-39D7-A407-A3E854153556> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff8da95000 -     0x7fff8dacfff7  com.apple.GSS (3.0 - 2.0) <423BDFCC-9187-3F3E-ABB0-D280003EB15E> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff8db27000 -     0x7fff8db7cff7  libTIFF.dylib (851) <7706BB07-E7E8-38BE-A5F0-D8B63E3B9283> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff8db7d000 -     0x7fff8db7dfff  com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff8db86000 -     0x7fff8db9bff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
    0x7fff8db9c000 -     0x7fff8dfb9fff  FaceCoreLight (2.4.1) <DDAFFD7A-D312-3407-A010-5AEF3E17831B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLight
    0x7fff8dfba000 -     0x7fff8e014fff  com.apple.print.framework.PrintCore (8.3 - 387.2) <5BA0CBED-4D80-386A-9646-F835C9805B71> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff8e015000 -     0x7fff8e082ff7  com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff8e235000 -     0x7fff8e2e6fff  com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff8e2e7000 -     0x7fff8e2effff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
    0x7fff8e333000 -     0x7fff8e35aff7  com.apple.PerformanceAnalysis (1.16 - 16) <E4888388-F41B-313E-9CBB-5807D077BDA9> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
    0x7fff8e35b000 -     0x7fff8e366fff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
    0x7fff8e367000 -     0x7fff8e395ff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
    0x7fff8e3e6000 -     0x7fff8e435ff7  libFontRegistry.dylib (100) <2E03D7DA-9B8F-31BB-8FB5-3D3B6272127F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff8e996000 -     0x7fff8e996fff  com.apple.Accelerate (1.8 - Accelerate 1.8) <878A6E7E-CB34-380F-8212-47FBF12C7C96> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff8e9ec000 -     0x7fff8ea0bff7  libresolv.9.dylib (51) <0882DC2D-A892-31FF-AD8C-0BB518C48B23> /usr/lib/libresolv.9.dylib
    0x7fff8eb26000 -     0x7fff8eb29ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
    0x7fff8eb2f000 -     0x7fff8eb4eff7  com.apple.ChunkingLibrary (2.0 - 133.3) <8BEC9AFB-DCAA-37E8-A5AB-24422B234ECF> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
    0x7fff8f0cd000 -     0x7fff8f39eff7  com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff8f46a000 -     0x7fff8f471fff  com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff8f472000 -     0x7fff8f510ff7  com.apple.ink.framework (10.8.2 - 150) <3D8D16A2-7E01-3EA1-B637-83A36D353308> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff8f511000 -     0x7fff8f511fff  com.apple.vecLib (3.8 - vecLib 3.8) <6CBBFDC4-415C-3910-9558-B67176447789> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff8f521000 -     0x7fff8f525fff  libGIF.dylib (851) <AD40D084-6E34-38CD-967D-705F94B188DA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff8f526000 -     0x7fff8f726fff  libicucore.A.dylib (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /usr/lib/libicucore.A.dylib
    0x7fff8f784000 -     0x7fff8f81ffff  com.apple.CoreSymbolication (3.0 - 117) <7D43ED93-BD81-338C-8076-6A932A1D19E8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff9020f000 -     0x7fff9025bff7  libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
    0x7fff902ad000 -     0x7fff90422ff7  com.apple.CFNetwork (596.5 - 596.5) <22372475-6EF4-3A04-83FC-C061FE4717B3> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff90773000 -     0x7fff90781fff  com.apple.Librarian (1.1 - 1) <5AC28666-7642-395F-A923-C6F8A274BBBD> /System/Library/PrivateFrameworks/Librarian.framework/Versions/A/Librarian
    0x7fff90782000 -     0x7fff90930fff  com.apple.QuartzCore (1.8 - 304.3) <F450F2DE-2F24-3557-98B6-310E05DAC17F> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff909d1000 -     0x7fff909e2ff7  libsasl2.2.dylib (166) <649CAE0E-8FFE-3C60-A849-BE6300E4B726> /usr/lib/libsasl2.2.dylib
    0x7fff919a3000 -     0x7fff919e6ff7  com.apple.RemoteViewServices (2.0 - 80.6) <5CFA361D-4853-3ACC-9EFC-A2AC1F43BA4B> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
    0x7fff919e7000 -     0x7fff91a1dfff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
    0x7fff91a1e000 -     0x7fff91a5dff7  com.apple.QD (3.42.1 - 285.1) <77A20C25-EBB5-341C-A05C-5D458B97AD5C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff91ac6000 -     0x7fff91c61fef  com.apple.vImage (6.0 - 6.0) <FAE13169-295A-33A5-8E6B-7C2CC1407FA7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff91c62000 -     0x7fff91d64fff  libcrypto.0.9.8.dylib (47.2) <CF3BAB7E-4972-39FD-AF92-28ACAFF0873E> /usr/lib/libcrypto.0.9.8.dylib
    0x7fff9290b000 -     0x7fff92912fff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
    0x7fff92913000 -     0x7fff92930ff7  com.apple.openscripting (1.3.6 - 148.3) <C008F56A-1E01-3D4C-A9AF-97799D0FAE69> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff92931000 -     0x7fff92940fff  com.apple.opengl (1.8.10 - 1.8.10) <AD49CF56-B7C1-3598-8610-58532FC41345> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff92941000 -     0x7fff92945fff  libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
    0x7fff92946000 -     0x7fff92959ff7  com.apple.LangAnalysis (1.7.0 - 1.7.0) <2F2694E9-A7BC-33C7-B4CF-8EC907DF0FEB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff9295a000 -     0x7fff92963ff7  com.apple.CommerceCore (1.0 - 26.2) <AF35874A-6FA7-328E-BE30-8BBEF0B741A8> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore
    0x7fff92964000 -     0x7fff92965ff7  libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
    0x7fff929b6000 -     0x7fff929fefff  libcurl.4.dylib (69.2) <EBDBF42D-E4A6-3D05-A76B-2817D79D59E2> /usr/lib/libcurl.4.dylib
    0x7fff92a49000 -     0x7fff92a71fff  libJPEG.dylib (851) <64A3EB03-34FB-308C-817B-6106D1F4D80F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff92af5000 -     0x7fff92e54fff  com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff92e55000 -     0x7fff92e76fff  com.apple.Ubiquity (1.2 - 243.15) <C9A7EE77-B637-3676-B667-C0843BBB0409> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
    0x7fff92e77000 -     0x7fff92e81fff  com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <D803919C-3102-3515-A178-61E9C86C46A1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff92e82000 -     0x7fff93008fff  libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff93009000 -     0x7fff93016ff7  com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff9309e000 -     0x7fff930a3fff  com.apple.OpenDirectory (10.8 - 151.10) <CF44120B-9B01-32DD-852E-C9C0E1243FC0> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff930a4000 -     0x7fff930f5ff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <A4341BBD-A330-3A57-8891-E9C1A286A72D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff93101000 -     0x7fff931d3ff7  com.apple.CoreText (260.0 - 275.17) <AB493289-E188-3CCA-8658-1E5039715F82> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff931d4000 -     0x7fff931d5ff7  libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff931d6000 -     0x7fff93204fff  com.apple.CoreServicesInternal (154.3 - 154.3) <F4E118E4-E327-3314-83D7-EA20B1717ED0> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff93205000 -     0x7fff93264fff  com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff93265000 -     0x7fff9326bfff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
    0x7fff9335e000 -     0x7fff933deff7  com.apple.ApplicationServices.ATS (332 - 341.1) <39B53565-FA31-3F61-B090-C787C983142E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff933df000 -     0x7fff933ebfff  com.apple.CrashReporterSupport (10.8.3 - 418) <DE6AFE16-D97E-399D-82ED-3522C773C36E> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
    0x7fff9341e000 -     0x7fff93424fff  com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff93480000 -     0x7fff93493ff7  libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
    0x7fff93494000 -     0x7fff934b5ff7  libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
    0x7fff934b6000 -     0x7fff934c2fff  libCSync.A.dylib (333.1) <319D3E83-8086-3990-8773-872F2E7C6EB3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x7fff934c3000 -     0x7fff934fbfff  libtidy.A.dylib (15.10) <9009156B-84F5-3781-BFCB-B409B538CD18> /usr/lib/libtidy.A.dylib
    0x7fff93557000 -     0x7fff93557ffd  com.apple.audio.units.AudioUnit (1.9.2 - 1.9.2) <6D314680-7409-3BC7-A807-36341411AF9A> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff93558000 -     0x7fff93584ff7  libRIP.A.dylib (333.1) <CC2A33EB-409C-3C4D-97D4-41F4A080F874> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x7fff93585000 -     0x7fff93603ff7  com.apple.securityfoundation (6.0 - 55115.4) <C5461971-E455-31A6-99B8-AF80C4BC26DD> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff938fe000 -     0x7fff9392cfff  com.apple.shortcut (2.2 - 2.2) <C573DB65-37FB-3DDC-AB19-525094346D9B> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
    0x7fff9393c000 -     0x7fff93a2dff7  com.apple.DiskImagesFramework (10.8.3 - 345) <F9FAEAF0-B9A5-34DF-94B7-926FB03AD5F6> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages
    0x7fff93a2e000 -     0x7fff93a45fff  com.apple.CFOpenDirectory (10.8 - 151.10) <FFBBA538-00B5-334E-BA5B-C8AD6CDCDA14> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff93a46000 -     0x7fff93a46fff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
    0x7fff93a97000 -     0x7fff93b18fff  com.apple.Metadata (10.7.0 - 707.12) <69E3EEF7-8B7B-3652-8320-B8E885370E56> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff93b19000 -     0x7fff93b26fff  com.apple.AppleFSCompression (49 - 1.0) <5508344A-2A7E-3122-9562-6F363910A80E> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff93b27000 -     0x7fff93b28ff7  libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib
    0x7fff93b31000 -     0x7fff93c04ff7  com.apple.DiscRecording (7.0 - 7000.2.4) <49FD2D2F-4F2C-39B6-877B-6E3172577D18> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff93c05000 -     0x7fff93c49fff  libcups.2.dylib (327.7) <9F35B58A-F47E-348A-8E09-E235FA4B9270> /usr/lib/libcups.2.dylib
    0x7fff93c4a000 -     0x7fff93c4cff7  com.apple.print.framework.Print (8.0 - 258) <34666CC2-B86D-3313-B3B6-A9977AD593DA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff93c6b000 -     0x7fff93c96fff  libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
    0x7fff93da6000 -     0x7fff93da6fff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff93da7000 -     0x7fff93dddfff  com.apple.DebugSymbols (98 - 98) <14E788B1-4EB2-3FD7-934B-849534DFC198> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
    0x7fff93dde000 -     0x7fff93ef692f  libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
    0x7fff93f03000 -     0x7fff93f9dfff  libvMisc.dylib (380.10) <A7F12764-A94C-36EB-88E0-F826F5AF55B4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff94052000 -     0x7fff94060fff  libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
    0x7fff94061000 -     0x7fff9415efff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
    0x7fff9415f000 -     0x7fff94186fff  com.apple.framework.familycontrols (4.1 - 410) <50F5A52C-8FB6-300A-977D-5CFDE4D5796B> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
    0x7fff94187000 -     0x7fff941ddfff  com.apple.HIServices (1.20 - 417) <839B4EE4-B96F-3371-BE90-3B4EBB86C6EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff941de000 -     0x7fff941edff7  libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
    0x7fff942ba000 -     0x7fff942ebff7  com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff942ec000 -     0x7fff942f0ff7  com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x7fff942f1000 -     0x7fff94c81627  com.apple.CoreGraphics (1.600.0 - 333.1) <C085C074-7260-3C3D-90C6-A65D3CB2BD41> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff95173000 -     0x7fff95200ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff95201000 -     0x7fff95204fff  com.apple.help (1.3.2 - 42) <343904FE-3022-3573-97D6-5FE17F8643BA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff95207000 -     0x7fff9551eff7  com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff9556b000 -     0x7fff95611ff7  com.apple.CoreServices.OSServices (557.6 - 557.6) <1BDB5456-0CE9-301C-99C1-8EFD0D2BFCCD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff956b5000 -     0x7fff956b5fff  libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
    0x7fff956b6000 -     0x7fff956beff7  libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff956bf000 -     0x7fff956bffff  com.apple.Accelerate.vecLib (3.8 - vecLib 3.8) <F565B686-24E2-39F2-ACC3-C5E4084476BE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff95743000 -     0x7fff95744fff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff95745000 -     0x7fff95745fff  com.apple.Carbon (154 - 155) <372716D2-6FA1-3611-8501-3DD1D4A6E8C8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff95746000 -     0x7fff95748fff  com.apple.TrustEvaluationAgent (2.0 - 23) <A97D348B-32BF-3E52-8DF2-59BFAD21E1A3> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
    0x7fff95772000 -     0x7fff95b69fff  libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff95bff000 -     0x7fff95c0dff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
    0x7fff95c10000 -     0x7fff95d12fff  libJP2.dylib (851) <26FFBDBF-9CCE-33D7-A45B-0A31C98DA37E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff95d15000 -     0x7fff95d16fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
    0x7fff95fe7000 -     0x7fff95febfff  libCGXType.A.dylib (333.1) <16625094-813E-39F8-9AFE-C1A24ED11749> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
    0x7fff95fec000 -     0x7fff96007ff7  libsystem_kernel.dylib (2050.48.12) <4B7993C3-F62D-3AC1-AF92-414A0D6EED5E> /usr/lib/system/libsystem_kernel.dylib
    0x7fff96008000 -     0x7fff9602aff7  libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
    0x7fff9602b000 -     0x7fff96032fff  libGFXShared.dylib (8.10.1) <B4AB9480-2CDB-34F8-8D6F-F5A2CFC221B0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff96033000 -     0x7fff9608aff7  com.apple.ScalableUserInterface (1.0 - 1) <F1D43DFB-1796-361B-AD4B-39F1EED3BE19> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface
    0x7fff96344000 -     0x7fff96351ff7  com.apple.HelpData (2.1.4 - 85) <EE68BDCC-AF2E-34D3-8E4F-87379E3A4D8E> /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
    0x7fff9636d000 -     0x7fff96372fff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
    0x7fff96373000 -     0x7fff96468fff  libiconv.2.dylib (34) <FEE8B996-EB44-37FA-B96E-D379664DEFE1> /usr/lib/libiconv.2.dylib
    0x7fff964b9000 -     0x7fff9660bfff  com.apple.audio.toolbox.AudioToolbox (1.9.2 - 1.9.2) <DC5F3D1B-036A-37DE-BC24-7636DC95EA1C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff9680e000 -     0x7fff9687cff7  com.apple.framework.IOKit (2.0.1 - 755.42.1) <A90038ED-48F2-3CC9-A042-53A3D7985844> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff96add000 -     0x7fff96b27ff7  libGLU.dylib (8.10.1) <6699DEA6-9EEB-3B84-A57F-B25AE44EC584> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff96b28000 -     0x7fff96c48fff  com.apple.desktopservices (1.7.4 - 1.7.4) <ED3DA8C0-160F-3CDC-B537-BF2E766AB7C1> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
    0x7fff96c49000 -     0x7fff96c54fff  com.apple.CommonAuth (3.0 - 2.0) <1CA95702-DDC7-3ADB-891E-7F037ABDDA14> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff96f19000 -     0x7fff96f1afff  liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
    0x7fff96f62000 -     0x7fff96f70ff7  libkxld.dylib (2050.48.12) <B8F7ED1F-CF84-3777-9183-0A1C513DF81F> /usr/lib/system/libkxld.dylib
    0x7fff97119000 -     0x7fff9717cfff  com.apple.audio.CoreAudio (4.1.2 - 4.1.2) <FEAB83AB-1DE5-3813-BA48-7A7F2374CCF0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff9717d000 -     0x7fff97181fff  com.apple.IOSurface (86.0.4 - 86.0.4) <26F01CD4-B76B-37A3-989D-66E8140542B3> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff97182000 -     0x7fff97184fff  libCVMSPluginSupport.dylib (8.10.1) <F0239392-E0CB-37D7-BFE2-D6F5D42F9196> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff97185000 -     0x7fff9718afff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
    0x7fff9718b000 -     0x7fff974bbfff  com.apple.HIToolbox (2.0 - 626.1) <656D08C2-9068-3532-ABDD-32EC5057CCB2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff97512000 -     0x7fff9760fff7  libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
    0x7fff97610000 -     0x7fff97626fff  com.apple.MultitouchSupport.framework (237.4 - 237.4) <0F7FEE29-161B-3D8E-BE91-308CBD354461> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff97627000 -     0x7fff976ecff7  com.apple.coreui (2.0 - 181.1) <83D2C92D-6842-3C9D-9289-39D5B4554C3A> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff979e5000 -     0x7fff979fcfff  com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
    0x7fff979fd000 -     0x7fff97a7fff7  com.apple.Heimdal (3.0 - 2.0) <ACF0C667-5ACC-382A-A998-61E85386C814> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff97a80000 -     0x7fff97ac0ff7  com.apple.MediaKit (14 - 687) <8AAA8CC3-3ACD-34A5-9E57-9B24AD8AFD4D> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
    0x7fff97ac1000 -     0x7fff97cabff7  com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff97cac000 -     0x7fff97ce7fff  com.apple.LDAPFramework (2.4.28 - 194.5) <7E4F2C08-0010-34AE-BC46-149B7EE8A0F5> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff97d04000 -     0x7fff97fa8ff7  com.apple.CoreImage (8.4.0 - 1.0.1) <CC6DD22B-FFC6-310B-BE13-2397A02C79EF> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff97fa9000 -     0x7fff97fc0fff  libGL.dylib (8.10.1) <F8BABA3C-7810-3A65-83FC-61945AA50E90> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff97fcb000 -     0x7fff98097ff7  libsystem_c.dylib (825.40.1) <543B05AE-CFA5-3EFE-8E58-77225411BA6B> /usr/lib/system/libsystem_c.dylib
    0x7fff98098000 -     0x7fff980f2ff7  com.apple.opencl (2.2.19 - 2.2.19) <3C7DFB2C-B3F9-3447-A1FC-EAAA42181A6E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff983a3000 -     0x7fff983b0fff  libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
    0x7fff983b1000 -     0x7fff983c5fff  com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <94EDF2AB-809C-3D15-BED5-7AD45B2A7C16> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff983c6000 -     0x7fff98422ff7  com.apple.Symbolication (1.3 - 93) <F2C7E0B6-B241-3020-B30A-0636D0FA3378> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
    0x7fff98423000 -     0x7fff9842eff7  com.apple.bsd.ServiceManagement (2.0 - 2.0) <C12962D5-85FB-349E-AA56-64F4F487F219> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff9842f000 -     0x7fff98432fff  libRadiance.dylib (851) <C317B2C7-CA3A-329F-B6DC-7CC33FE08C81> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff9844e000 -     0x7fff9846efff  libPng.dylib (851) <3466F35C-EC1A-3D1A-80DC-175857FA19D5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff98489000 -     0x7fff984b3ff7  com.apple.CoreVideo (1.8 - 99.4) <E5082966-6D81-3973-A05A-38AA5B85F886> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff984b4000 -     0x7fff9851cff7  libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
    0x7fff986bb000 -     0x7fff986f4ff7  libssl.0.9.8.dylib (47.2) <46DF85DC-18FB-3108-91F6-52AE3EBF2347> /usr/lib/libssl.0.9.8.dylib
    0x7fff98ce9000 -     0x7fff98cedfff  libCoreVMClient.dylib (32.5) <DB009CD4-BB0E-3331-BBB4-A118781D193F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff98cee000 -     0x7fff9991bfff  com.apple.AppKit (6.8 - 1187.40) <F12CF463-6F88-32ED-9EBA-0FA2AD3CF576> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff9991c000 -     0x7fff999f6fff  com.apple.backup.framework (1.4.3 - 1.4.3) <6B65C44C-7777-3331-AD9D-438D10AAC777> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff99a4e000 -     0x7fff99a50fff  libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib
    0x7fff99a5a000 -     0x7fff99aa9ff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib

[etotheipi]

Code:

2013-11-17 00:29 (INFO) -- ArmoryQt.py:1633 - loadWalletsAndSettings
2013-11-17 00:29 (INFO) -- ArmoryQt.py:1680 - Loading wallets...
2013-11-17 00:29 (WARNING) -- armoryengine.py:9074 - ***WARNING: creation of backup was interrupted -- fixing
2013-11-17 00:29 (ERROR) -- ArmoryQt.py:1723 - ***WARNING: Wallet could not be loaded: /home/ferret/.armory/armory_35Fijn44X_.watchonly.wallet (skipping)
...
OSError: [Errno 1] Operation not permitted: '/home/ferret/.armory/armory_35Fijn44X_.watchonly_backup.wallet'

SimonL, you definitely earned your bounty!  Thanks for looking into that!  The fact that you do have a corrupted/malformed wallet file confirms that this is probably related to the last person who reported this.  They removed the corrupted file and the behavior went away.  It sounds like perhaps you just need to remove the WO wallet and re-export the watching-only wallet from the offline computer, to replace the corrupted one (it looks like Armory couldn't fix it).  Unfortuantely, it doesn't carry the comments with it... will add that as a later feature (to merge wallet files).

I left Armory on for some time and it's crashed:
Log from console:

Code:

...

Do you have a lot of addresses?  This particular crash looks like what happens when Armory gets "swamped" in processing, and falls behind trying to catch up.  Still some errors in my error-handling procedures, but I haven't seen it happen under nominal conditions.  There's definitely some room for improvement there...

I don't know is this bug but always when i close Armory:

Code:

-INFO  - 1384625610: (BlockUtils.cpp:3999) Saving wallet history for next load
(ERROR) armoryengine.py:13216 - Resetting BDM and all wallets
(WARNING) armoryengine.py:661 - Killing process pid=8379
(ERROR) ArmoryQt.py:4337 - BitcoindNotAvailable: should not happen...
Resetting BlockDataMgr, freeing memory

That's actually somewhat normal.  It's an "error" in a code path sense, but simply because something it was trying to do was already done. I should fix the messages...

I'm running OSX 10.8, every so often I'll get a dialog saying armory is not in sync because bitcoind/QT is off, however the QT app never quits. My laptop sometimes goes into power save mode, which disables the wifi, I think. Not sure if that has anything to do with it, but I tend to notice it more when waking up my mac. It doesn't just pop up at random while I'm active on it.

Yeah, Armory has always had a problem with this.  I think it would be a serious project to fix this.  Right now I guess we should add to the documentation that you need to disable sleep/power-save if you want to keep Armory running all the time.  However, now that its startup time is dramatically reduced, it's not so terrible to close it when you're done ...

• Restoring paper and digital backups without restarting the app

I restored two wallets after building the database.  The first rescanned fine. The second hung at 0% after the error: 
Traceback (most recent call last):
  File "armoryengine.pyc", line 13409, in run
  File "armoryengine.pyc", line 13051, in __startRescanBlockchain
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'I:\\armory\\blkfiles.txt'

After closing and opening Armory the rescan is going now.

Code:

...

Ahh, super interesting.  There's a file that stores the scan state, and it's apparently not being released from the previous scan, in order to be opened for the next one.  I will look at that.  1x bounty for you!

Mac OSX 10.8.5 Crash

Code:

...

Can you please open Armory and use "File"->Export Log File and email the result to support @ bitcoinarmory.com?  Those crash reports are pretty much useless for us.  It gives us a tiny hint of where the problem is, but the log gives us the whole story.  And please use the menu, since there's multiple logs that Armory will collapse into one.   Or maybe you can find some interesting error messages in the log and post them here.

[devthedev]

Issue with auto scroll up, Windows 8 Pro. 64bit. 8GB RAM. I encountered this bug while using Armory 0.89.99.14-beta / Advanced.. --- Video of the bug below.

http://www.screenr.com/N6QH

Let me know if this helps.

1NjgWevCNQ3XbzAmqr2V3tdTxGwozgYPUT

The same problem exists in OSX, Version 10.9 - 2.53 GHz Intel Core Duo, 4GB DDR3.

Not sure if this qualifies for another bounty but, here you have it

Let me know if you want a screen capture of the bug in Mavericks.

[Mooshire]

Hi, I sent .1 BTC to my armory address running this version (Windows 8, 8 GB RAM) and whenever I do anything that requires unlocking my wallet, it completely freezes and becomes unresponsive. I have a paper backup. Help?

[PRab]

Minor usability issue (no bounty expected). When creating a new wallet Armory asks for your password 3 times while creating it then immediately asks a 4th time so that it can do a backup. I think Armory should automatically remember the password internally when launching the backup manager.

Edit: Also, canceling out of the backup manager asks if you want to test the backup. Obviously you can't test the backup because you didn't make it.

Finally, when making an new wallet, I would prefer Armory allow the user to pick the type of backup instead of just assuming a single page paper backup.

Edit 2: The "Done" option on the backup center screen acts like a cancel button and I would recommend rewording the label. Armory uses "<<< Go Back" on the wallet properties screen so that could be used for consistency.

Edit 3 (sorry...): Also on the backup center screen, the text in the features of the backup type (right box) moves around depending on which option is selected. The text stays the same, so why does the text move. (Windows 7 64bit) I can take some screenshots to show the issue if needed, but I think it is because the x icon is a different size than the checkmark.

Edit 4 (I swear this is the last): The "Done" option on the backup center doesn't force the focus back to another Armory screen. For example bring up the backup center, switch windows to firefox (fullscreen), switch back to the backup center, click "Done". This drops you back to firefox instead of Armory.

[redphlegm]

Mac OSX 10.8.5 Crash

Code:

...

Can you please open Armory and use "File"->Export Log File and email the result to support @ bitcoinarmory.com?  Those crash reports are pretty much useless for us.  It gives us a tiny hint of where the problem is, but the log gives us the whole story.  And please use the menu, since there's multiple logs that Armory will collapse into one.   Or maybe you can find some interesting error messages in the log and post them here.

emailed as attachment using what I think is your public key for file encryption. Let me know if I need to send it a different way.

Thanks.

[SimonL]

Code:

2013-11-17 00:29 (INFO) -- ArmoryQt.py:1633 - loadWalletsAndSettings
2013-11-17 00:29 (INFO) -- ArmoryQt.py:1680 - Loading wallets...
2013-11-17 00:29 (WARNING) -- armoryengine.py:9074 - ***WARNING: creation of backup was interrupted -- fixing
2013-11-17 00:29 (ERROR) -- ArmoryQt.py:1723 - ***WARNING: Wallet could not be loaded: /home/ferret/.armory/armory_35Fijn44X_.watchonly.wallet (skipping)
...
OSError: [Errno 1] Operation not permitted: '/home/ferret/.armory/armory_35Fijn44X_.watchonly_backup.wallet'

SimonL, you definitely earned your bounty!  Thanks for looking into that!  The fact that you do have a corrupted/malformed wallet file confirms that this is probably related to the last person who reported this.  They removed the corrupted file and the behavior went away.  It sounds like perhaps you just need to remove the WO wallet and re-export the watching-only wallet from the offline computer, to replace the corrupted one (it looks like Armory couldn't fix it).  Unfortuantely, it doesn't carry the comments with it... will add that as a later feature (to merge wallet files).

No worries, glad I can help out

I re-exported the watching-only wallet using my offline version 0.88.1-beta but it still threw back the same error, so it seems that something with exporting that particular wallet doesn't agree with the newer version. I'm pretty sure that the watching only wallet that failed was made using 0.88.1 and the other wallets were created using an earlier version, though I'm not 100% certain.

[128bpm]

https://codereview.qt-project.org/#change,62937
seems to have a patch that is working to solve the 10.9 Modal sessions issues on Mac.

EDIT: the current build script is using a precompiled version of Qt, targeted at Mountain Lion.  Maybe try building Qt from scratch (using the homebrew formula for inspiration) and adding this patch.

[cp1]

I restored two wallets after building the database.  The first rescanned fine. The second hung at 0% after the error: 
Traceback (most recent call last):
  File "armoryengine.pyc", line 13409, in run
  File "armoryengine.pyc", line 13051, in __startRescanBlockchain
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'I:\\armory\\blkfiles.txt'

Ahh, super interesting.  There's a file that stores the scan state, and it's apparently not being released from the previous scan, in order to be opened for the next one.  I will look at that.  1x bounty for you!

Score!  You can send it to:  1TipMeWsx7KNoX6Lap3Vh3PM8B8EYuRJj
Thanks for all your hard work.

[morningtime]

-never mind-

[greBit]

I don't seem to be able to shutdown cleanly, and thus Armory requires a slow re-scan of the blockchain each time I load it.

Running on Ubuntu 12.04 / 64 bit

Heres a log of some of the output upon closing Armory:

Code:

(ERROR) armoryengine.py:11770 - BDM was not ready for your request!  Waited 10 sec.
(ERROR) armoryengine.py:11771 -   getattr   name: hasTxWithHash
(ERROR) armoryengine.py:11772 - BDM currently doing: Shutdown (49332375)
(ERROR) armoryengine.py:11773 - Waiting for completion: ID= 20812363
(ERROR) armoryengine.py:11774 - Direct traceback
  File "ArmoryQt.py", line 4824, in <module>
    os._exit(QAPP.exec_())
  File "/opt/bitcoin-armory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 84, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 69, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/bitcoin-armory/qt4reactor.py", line 92, in _read
    why = w.doRead()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line 199, in doRead
    rval = self.protocol.dataReceived(data)
  File "/opt/bitcoin-armory/armoryengine.py", line 10101, in dataReceived
    self.processMessage(msg)
  File "/opt/bitcoin-armory/armoryengine.py", line 10129, in processMessage
    TheBDM.hasTxWithHash(inv[1]):
  File "/opt/bitcoin-armory/armoryengine.py", line 11775, in passthruFunc
    traceback.print_stack()
(ERROR) armoryengine.py:11777 - Traceback:
Traceback (most recent call last):
  File "/opt/bitcoin-armory/armoryengine.py", line 11767, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
(ERROR) armoryengine.py:11796 - Waiting for BDM output that didn't come after 10s.
(ERROR) armoryengine.py:11797 - BDM state is currently: BlockchainReady
(ERROR) armoryengine.py:11798 - Called from: armoryengine.py:11964 (11801336)
(ERROR) armoryengine.py:11799 - BDM currently doing: Shutdown (49332375)
(ERROR) armoryengine.py:11800 - Direct traceback
  File "ArmoryQt.py", line 4824, in <module>
    os._exit(QAPP.exec_())
  File "/opt/bitcoin-armory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 84, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 69, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/bitcoin-armory/qt4reactor.py", line 102, in _read
    self.reactor._iterate(fromqt=True)
  File "/opt/bitcoin-armory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4415, in Heartbeat
    newBlocks = TheBDM.readBlkFileUpdate(wait=True)
  File "/opt/bitcoin-armory/armoryengine.py", line 11964, in readBlkFileUpdate
    return self.waitForOutputIfNecessary(expectOutput, rndID)
  File "/opt/bitcoin-armory/armoryengine.py", line 11801, in waitForOutputIfNecessary
    traceback.print_stack()
(ERROR) armoryengine.py:11802 - Traceback:
Traceback (most recent call last):
  File "/opt/bitcoin-armory/armoryengine.py", line 11792, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
(ERROR) armoryengine.py:11770 - BDM was not ready for your request!  Waited 10 sec.
(ERROR) armoryengine.py:11771 -   getattr   name: getTopBlockHeight
(ERROR) armoryengine.py:11772 - BDM currently doing: Shutdown (49332375)
(ERROR) armoryengine.py:11773 - Waiting for completion: ID= 54154651
(ERROR) armoryengine.py:11774 - Direct traceback
  File "ArmoryQt.py", line 4824, in <module>
    os._exit(QAPP.exec_())
  File "/opt/bitcoin-armory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 84, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 69, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/bitcoin-armory/qt4reactor.py", line 102, in _read
    self.reactor._iterate(fromqt=True)
  File "/opt/bitcoin-armory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4416, in Heartbeat
    self.currBlockNum = TheBDM.getTopBlockHeight()
  File "/opt/bitcoin-armory/armoryengine.py", line 11775, in passthruFunc
    traceback.print_stack()
(ERROR) armoryengine.py:11777 - Traceback:
Traceback (most recent call last):
  File "/opt/bitcoin-armory/armoryengine.py", line 11767, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
(ERROR) armoryengine.py:11770 - BDM was not ready for your request!  Waited 10 sec.
(ERROR) armoryengine.py:11771 -   getattr   name: rescanWalletZeroConf
(ERROR) armoryengine.py:11772 - BDM currently doing: Shutdown (49332375)
(ERROR) armoryengine.py:11773 - Waiting for completion: ID= 31095303
(ERROR) armoryengine.py:11774 - Direct traceback
  File "ArmoryQt.py", line 4824, in <module>
    os._exit(QAPP.exec_())
  File "/opt/bitcoin-armory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 84, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 69, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/bitcoin-armory/qt4reactor.py", line 102, in _read
    self.reactor._iterate(fromqt=True)
  File "/opt/bitcoin-armory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4447, in Heartbeat
    TheBDM.rescanWalletZeroConf(wlt.cppWallet, wait=True)
  File "/opt/bitcoin-armory/armoryengine.py", line 11775, in passthruFunc
    traceback.print_stack()
(ERROR) armoryengine.py:11777 - Traceback:
Traceback (most recent call last):
  File "/opt/bitcoin-armory/armoryengine.py", line 11767, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
(ERROR) armoryengine.py:11770 - BDM was not ready for your request!  Waited 10 sec.
(ERROR) armoryengine.py:11771 -   getattr   name: rescanWalletZeroConf
(ERROR) armoryengine.py:11772 - BDM currently doing: Shutdown (49332375)
(ERROR) armoryengine.py:11773 - Waiting for completion: ID= 98820070
(ERROR) armoryengine.py:11774 - Direct traceback
  File "ArmoryQt.py", line 4824, in <module>
    os._exit(QAPP.exec_())
  File "/opt/bitcoin-armory/qt4reactor.py", line 103, in read
    log.callWithLogger(w, _read)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 84, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/log.py", line 69, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 118, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, in callWithContext
    return func(*args,**kw)
  File "/opt/bitcoin-armory/qt4reactor.py", line 102, in _read
    self.reactor._iterate(fromqt=True)
  File "/opt/bitcoin-armory/qt4reactor.py", line 231, in _iterate
    self.runUntilCurrent()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "ArmoryQt.py", line 4447, in Heartbeat
    TheBDM.rescanWalletZeroConf(wlt.cppWallet, wait=True)
  File "/opt/bitcoin-armory/armoryengine.py", line 11775, in passthruFunc
    traceback.print_stack()
(ERROR) armoryengine.py:11777 - Traceback:
Traceback (most recent call last):
  File "/opt/bitcoin-armory/armoryengine.py", line 11767, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
Resetting BlockDataMgr, freeing memory

[jyyst]

Do you have a lot of addresses?  This particular crash looks like what happens when Armory gets "swamped" in processing, and falls behind trying to catch up.  Still some errors in my error-handling procedures, but I haven't seen it happen under nominal conditions.  There's definitely some room for improvement there...

3 wallets, 1st - 71 used addresses, 2nd - 73 used addresses, 3th - 35 used addresses. So it's 179 used addresses.

[picobit]

https://codereview.qt-project.org/#change,62937
seems to have a patch that is working to solve the 10.9 Modal sessions issues on Mac.

EDIT: the current build script is using a precompiled version of Qt, targeted at Mountain Lion.  Maybe try building Qt from scratch (using the homebrew formula for inspiration) and adding this patch.

etotheipi found that patch a few days ago.  I already modified the build script to build Qt from source.  Requires the git head and 2-3 patches just to compile.  Unfortunately only to find out that the patch you referred to makes no difference.  My guess is that the patch does not solve the actual problem, but only the symptom, and that the real trouble is elsewhere (possibly in OS X and not in Qt).

[justusranvier]

Code:

2013-11-17 21:38 (INFO) -- armoryengine.py:12398 - Reading blockchain, pct complete: 99.6
2013-11-17 21:39 (INFO) -- armoryengine.py:12398 - Reading blockchain, pct complete: 0.0
2013-11-17 21:39 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 2qx2YAzB
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: hfGoBPCT
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: v7K4ZC15
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 2mKi33bH9
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: GeZiZcDD
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: umjPW8pw
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 21ZeYZai3
2013-11-17 21:39 (INFO) -- ArmoryQt.py:1926 - Current block number: 270232
2013-11-17 21:39 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-17 21:39 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online"
2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-17 21:50 (INFO) -- ArmoryQt.py:4786 - New Block! : 270233
2013-11-17 21:50 (INFO) -- ArmoryQt.py:4810 - Current block number: 270233
2013-11-17 22:05 (INFO) -- armoryengine.py:10553 - Received new block.  00000000000000055f457b8f2c189e90a045f153d42c6afb940cd7b8bc8105ad
2013-11-17 22:05 (INFO) -- ArmoryQt.py:4786 - New Block! : 270234
2013-11-17 22:05 (INFO) -- ArmoryQt.py:4810 - Current block number: 270234
2013-11-17 22:41 (INFO) -- armoryengine.py:10553 - Received new block.  0000000000000002059e7f0c251de4ca86e73d8d8dbb8f3cf9d071114d4cc0a5
2013-11-17 22:41 (INFO) -- ArmoryQt.py:4786 - New Block! : 270235
2013-11-17 22:41 (INFO) -- ArmoryQt.py:4810 - Current block number: 270235
2013-11-17 22:47 (INFO) -- armoryengine.py:10553 - Received new block.  000000000000000656e968d866a3a3b6fb4edbecfc1f49e2e8b36becf82f04dc
2013-11-17 22:47 (INFO) -- ArmoryQt.py:4786 - New Block! : 270236
2013-11-17 22:47 (INFO) -- ArmoryQt.py:4810 - Current block number: 270236
2013-11-17 22:52 (INFO) -- armoryengine.py:10553 - Received new block.  000000000000000649500b42bfd07ffe586a0074f5b2fcfe9445b2053b82b4c8
2013-11-17 22:52 (INFO) -- ArmoryQt.py:4786 - New Block! : 270237
2013-11-17 22:52 (INFO) -- ArmoryQt.py:4810 - Current block number: 270237
2013-11-17 22:53 (INFO) -- armoryengine.py:10553 - Received new block.  0000000000000000060cbaf02710e7c891e06ec9eebada6e572324a685e1cbd6
2013-11-17 22:53 (INFO) -- ArmoryQt.py:4786 - New Block! : 270238
2013-11-17 22:53 (INFO) -- ArmoryQt.py:4810 - Current block number: 270238
2013-11-17 22:59 (INFO) -- ArmoryQt.py:4786 - New Block! : 270239
2013-11-17 22:59 (INFO) -- ArmoryQt.py:4810 - Current block number: 270239
2013-11-17 22:59 (INFO) -- armoryengine.py:10553 - Received new block.  0000000000000000249f70ff362231538dd50ba936ab5f60c01196e75404505a
2013-11-17 23:00 (ERROR) -- armoryengine.py:12265 - BDM was not ready for your request!  Waited 20 sec.
2013-11-17 23:00 (ERROR) -- armoryengine.py:12266 -   getattr   name: hasTxWithHash
2013-11-17 23:00 (ERROR) -- armoryengine.py:12267 - BDM currently doing: ZeroConfTxToInsert (57537226)
2013-11-17 23:00 (ERROR) -- armoryengine.py:12268 - Waiting for completion: ID= 55370105
2013-11-17 23:00 (ERROR) -- armoryengine.py:12269 - Direct traceback
2013-11-17 23:00 (ERROR) -- armoryengine.py:12272 - Traceback:
Traceback (most recent call last):
  File "/usr/lib64/armory/armoryengine.py", line 12262, in passthruFunc
    out = self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib64/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2013-11-17 23:00 (ERROR) -- armoryengine.py:13208 - ErrorOut var over-represented number of errors!

[ACVentures]

OSX 10.8, armory testing v14. I'm receiving an error slightly similar to the poster above:

Code:

2013-11-19 13:34 (INFO) -- ArmoryQt.py:4803 - Current block number: 270488
2013-11-19 14:17 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-11-19 14:17 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-11-19 14:17 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (20743723)
2013-11-19 14:17 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ZeroConfTxToInsert (14629250)
2013-11-19 14:17 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-11-19 14:17 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/Users/joeschmoe/BitcoinArmory/osx_picobit/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/Queue.py", line 176, in get
Empty
2013-11-19 14:17 (ERROR) -- armoryengine.py:13289 - ErrorOut var over-represented number of errors!
 

I'm guessing this to be related to coming out of screen saver/sleep mode. My bitcoin-QT manages to pick up the connection after a moment, but sometimes it may cause armory to crash. Usually there is no error in the armory log file. This happens a 1-3 times a day. Every time it happens, armory needs to rescan the blockchain (20-30min) and then it's normal.

Here is the relevant section from the system crash/hang log. It looks like thread #2 is the one that crashed, so that's what I copied:

Code:

Process:         Python [66359]
Path:            /Applications/Armory.app/Contents/MacOS/Python
Identifier:      com.armory.armory
Version:         ???
Code Type:       X86-64 (Native)
Parent Process:  bash [66356]
User ID:         501

Date/Time:       2013-11-19 14:17:28.853 -0500
OS Version:      Mac OS X 10.8.5 (12F45)
Report Version:  10
Sleep/Wake UUID: 3175AE78-633C-412C-B9D9-09218547AFC1

Crashed Thread:  2

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
--> 
    __TEXT                 0000000100000000-0000000100001000 [    4K] r-x/rwx SM=COW  /Applications/Armory.app/Contents/MacOS/Python

-------snip-------


Thread 2 Crashed:
0   _CppBlockUtils.so             	0x0000000103943c13 BtcWallet::isMineBulkFilter(Tx&, std::__1::map<OutPoint, TxIOPair, std::__1::less<OutPoint>, std::__1::allocator<std::__1::pair<OutPoint const, TxIOPair> > >&, bool) + 259
1   _CppBlockUtils.so             	0x00000001039476f8 BtcWallet::scanTx(Tx&, unsigned int, unsigned int, unsigned int) + 120
2   _CppBlockUtils.so             	0x0000000103957675 BlockDataManager_LevelDB::rescanWalletZeroConf(BtcWallet&) + 277
3   _CppBlockUtils.so             	0x0000000103b2434c _wrap_BlockDataManager_LevelDB_rescanWalletZeroConf + 172
4   org.python.python             	0x00000001000a5655 PyEval_EvalFrameEx + 16725
5   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
6   org.python.python             	0x0000000100033556 function_call + 342
7   org.python.python             	0x000000010000fe25 PyObject_Call + 101
8   org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
9   org.python.python             	0x00000001000a81e2 fast_function + 194
10  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
11  org.python.python             	0x00000001000a81e2 fast_function + 194
12  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
13  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
14  org.python.python             	0x0000000100033556 function_call + 342
15  org.python.python             	0x000000010000fe25 PyObject_Call + 101
16  org.python.python             	0x000000010001be46 instancemethod_call + 166
17  org.python.python             	0x000000010000fe25 PyObject_Call + 101
18  org.python.python             	0x00000001000a79ad PyEval_CallObjectWithKeywords + 93
19  org.python.python             	0x00000001000def26 t_bootstrap + 70
20  libsystem_c.dylib             	0x00007fff88351772 _pthread_start + 327
21  libsystem_c.dylib             	0x00007fff8833e1a1 thread_start + 13

-----snip-----

Thread 2 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000103cad240  rcx: 0x0000000000000000  rdx: 0x000000010f59bd78
  rdi: 0x0000000106000130  rsi: 0x000000010901efb0  rbp: 0x0000000105fffa90  rsp: 0x0000000105fff820
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000001002  r11: 0x00000001c8f22000
  r12: 0x0000000103cad260  r13: 0x000000010901efb0  r14: 0x000000010f59bd78  r15: 0x0000000000000000
  rip: 0x0000000103943c13  rfl: 0x0000000000010202  cr2: 0x0000000000000000
Logical CPU: 0

Hope this helps

[ACVentures]

OSX 10.8, testing v14. Crashed again unexpectedly. This time I'm confident I was active on the computer and it was not coming out of a recent sleep mode.

I had actually just created an offline cold wallet on a windows version (the 88 beta, not testing) and had imported it into armory OSX as watch only. OSX had just finished scanning the blockchain for the new watch only wallet addition, and regained sync with the current block height. Then a few moments later promptly crashed.

I tried to include the entire crash log but it looks like it's too big to post. Here's everything minus the Binary Images section:

Code:

Process:         Python [71648]
Path:            /Applications/Armory.app/Contents/MacOS/Python
Identifier:      com.armory.armory
Version:         ???
Code Type:       X86-64 (Native)
Parent Process:  bash [71645]
User ID:         501

Date/Time:       2013-11-19 22:04:55.902 -0500
OS Version:      Mac OS X 10.8.5 (12F45)
Report Version:  10

Crashed Thread:  2

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
--> 
    __TEXT                 0000000100000000-0000000100001000 [    4K] r-x/rwx SM=COW  /Applications/Armory.app/Contents/MacOS/Python

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff8be43322 __select + 10
1   time.so                       	0x00000001011399af time_sleep + 143
2   org.python.python             	0x00000001000a3320 PyEval_EvalFrameEx + 7712
3   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
4   org.python.python             	0x00000001000a8246 fast_function + 294
5   org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
6   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
7   org.python.python             	0x00000001000a8246 fast_function + 294
8   org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
9   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
10  org.python.python             	0x00000001000a8246 fast_function + 294
11  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
12  org.python.python             	0x00000001000a81e2 fast_function + 194
13  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
14  org.python.python             	0x00000001000a81e2 fast_function + 194
15  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
16  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
17  org.python.python             	0x00000001000a8246 fast_function + 294
18  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
19  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
20  org.python.python             	0x00000001000a8246 fast_function + 294
21  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
22  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
23  org.python.python             	0x0000000100033556 function_call + 342
24  org.python.python             	0x000000010000fe25 PyObject_Call + 101
25  org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
26  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
27  org.python.python             	0x0000000100033556 function_call + 342
28  org.python.python             	0x000000010000fe25 PyObject_Call + 101
29  org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
30  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
31  org.python.python             	0x0000000100033556 function_call + 342
32  org.python.python             	0x000000010000fe25 PyObject_Call + 101
33  org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
34  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
35  org.python.python             	0x0000000100033556 function_call + 342
36  org.python.python             	0x000000010000fe25 PyObject_Call + 101
37  org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
38  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
39  org.python.python             	0x00000001000a8246 fast_function + 294
40  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
41  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
42  org.python.python             	0x0000000100033556 function_call + 342
43  org.python.python             	0x000000010000fe25 PyObject_Call + 101
44  org.python.python             	0x000000010001be46 instancemethod_call + 166
45  org.python.python             	0x000000010000fe25 PyObject_Call + 101
46  org.python.python             	0x00000001000a79ad PyEval_CallObjectWithKeywords + 93
47  sip.so                        	0x000000010132b43c sip_api_invoke_slot + 401
48  QtCore.so                     	0x0000000101707709 PyQtProxy::invokeSlot(qpycore_slot const&, void**) + 169
49  QtCore.so                     	0x00000001017075b0 PyQtProxy::unislot(void**) + 160
50  QtCore.so                     	0x00000001017074fe PyQtProxy::qt_metacall(QMetaObject::Call, int, void**) + 110
51  QtCore                        	0x000000010198299e QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1912
52  QtCore                        	0x00000001019c1543 QSocketNotifier::activated(int) + 45
53  QtCore                        	0x0000000101986d7d QSocketNotifier::event(QEvent*) + 385
54  QtCore.so                     	0x00000001016a8932 sipQSocketNotifier::event(QEvent*) + 98
55  QtGui                         	0x0000000105052488 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 198
56  QtGui                         	0x0000000105054aa7 QApplication::notify(QObject*, QEvent*) + 5733
57  QtGui.so                      	0x0000000104846dd9 sipQApplication::notify(QObject*, QEvent*) + 121
58  QtCore                        	0x000000010196f639 QCoreApplication::notifyInternal(QObject*, QEvent*) + 101
59  QtGui                         	0x000000010500f8a6 qt_mac_socket_callback(__CFSocket*, unsigned long, __CFData const*, void const*, void*) + 146
60  com.apple.CoreFoundation      	0x00007fff90389fa5 __CFSocketPerformV0 + 1045
61  com.apple.CoreFoundation      	0x00007fff9034ab31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
62  com.apple.CoreFoundation      	0x00007fff9034a455 __CFRunLoopDoSources0 + 245
63  com.apple.CoreFoundation      	0x00007fff9036d7f5 __CFRunLoopRun + 789
64  com.apple.CoreFoundation      	0x00007fff9036d0e2 CFRunLoopRunSpecific + 290
65  com.apple.HIToolbox           	0x00007fff8e10beb4 RunCurrentEventLoopInMode + 209
66  com.apple.HIToolbox           	0x00007fff8e10bc52 ReceiveNextEventCommon + 356
67  com.apple.HIToolbox           	0x00007fff8e10bae3 BlockUntilNextEventMatchingListInMode + 62
68  com.apple.AppKit              	0x00007fff88bdb533 _DPSNextEvent + 685
69  com.apple.AppKit              	0x00007fff88bdadf2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
70  com.apple.AppKit              	0x00007fff88bd21a3 -[NSApplication run] + 517
71  QtGui                         	0x000000010500fe01 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 461
72  QtCore                        	0x000000010196cd89 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 79
73  QtCore                        	0x000000010196cee7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 341
74  QtCore                        	0x000000010196fa6b QCoreApplication::exec() + 199
75  QtGui.so                      	0x0000000104848330 meth_QApplication_exec_ + 80
76  org.python.python             	0x00000001000a3320 PyEval_EvalFrameEx + 7712
77  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
78  org.python.python             	0x00000001000a0cb6 PyEval_EvalCode + 54
79  org.python.python             	0x00000001000c8351 PyRun_FileExFlags + 161
80  org.python.python             	0x00000001000c7e9e PyRun_SimpleFileExFlags + 718
81  org.python.python             	0x00000001000dcedb Py_Main + 3307
82  Python                        	0x0000000100000e55 0x100000000 + 3669
83  Python                        	0x0000000100000d71 0x100000000 + 3441

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x00007fff8be43d16 kevent + 10
1   libdispatch.dylib             	0x00007fff8d921dea _dispatch_mgr_invoke + 883
2   libdispatch.dylib             	0x00007fff8d9219ee _dispatch_mgr_thread + 54

Thread 2 Crashed:
0   _CppBlockUtils.so             	0x0000000106943c13 BtcWallet::isMineBulkFilter(Tx&, std::__1::map<OutPoint, TxIOPair, std::__1::less<OutPoint>, std::__1::allocator<std::__1::pair<OutPoint const, TxIOPair> > >&, bool) + 259
1   _CppBlockUtils.so             	0x00000001069476f8 BtcWallet::scanTx(Tx&, unsigned int, unsigned int, unsigned int) + 120
2   _CppBlockUtils.so             	0x0000000106957675 BlockDataManager_LevelDB::rescanWalletZeroConf(BtcWallet&) + 277
3   _CppBlockUtils.so             	0x0000000106b2434c _wrap_BlockDataManager_LevelDB_rescanWalletZeroConf + 172
4   org.python.python             	0x00000001000a5655 PyEval_EvalFrameEx + 16725
5   org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
6   org.python.python             	0x0000000100033556 function_call + 342
7   org.python.python             	0x000000010000fe25 PyObject_Call + 101
8   org.python.python             	0x00000001000a57f6 PyEval_EvalFrameEx + 17142
9   org.python.python             	0x00000001000a81e2 fast_function + 194
10  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
11  org.python.python             	0x00000001000a81e2 fast_function + 194
12  org.python.python             	0x00000001000a459b PyEval_EvalFrameEx + 12443
13  org.python.python             	0x00000001000a1386 PyEval_EvalCodeEx + 1734
14  org.python.python             	0x0000000100033556 function_call + 342
15  org.python.python             	0x000000010000fe25 PyObject_Call + 101
16  org.python.python             	0x000000010001be46 instancemethod_call + 166
17  org.python.python             	0x000000010000fe25 PyObject_Call + 101
18  org.python.python             	0x00000001000a79ad PyEval_CallObjectWithKeywords + 93
19  org.python.python             	0x00000001000def26 t_bootstrap + 70
20  libsystem_c.dylib             	0x00007fff88351772 _pthread_start + 327
21  libsystem_c.dylib             	0x00007fff8833e1a1 thread_start + 13

Thread 3:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        	0x00007fff8be43322 __select + 10
1   com.apple.CoreFoundation      	0x00007fff903acf46 __CFSocketManager + 1302
2   libsystem_c.dylib             	0x00007fff88351772 _pthread_start + 327
3   libsystem_c.dylib             	0x00007fff8833e1a1 thread_start + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff8be430fa __psynch_cvwait + 10
1   libsystem_c.dylib             	0x00007fff88355fb9 _pthread_cond_wait + 869
2   _CppBlockUtils.so             	0x0000000106a668a7 leveldb::(anonymous namespace)::PosixEnv::BGThreadWrapper(void*) + 71
3   libsystem_c.dylib             	0x00007fff88351772 _pthread_start + 327
4   libsystem_c.dylib             	0x00007fff8833e1a1 thread_start + 13

Thread 2 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000106cad240  rcx: 0x0000000000000000  rdx: 0x0000000122faeb68
  rdi: 0x0000000107d00130  rsi: 0x000000010a8ebfa0  rbp: 0x0000000107cffa90  rsp: 0x0000000107cff820
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000001002  r11: 0x00000001cbb97000
  r12: 0x0000000106cad260  r13: 0x000000010a8ebfa0  r14: 0x0000000122faeb68  r15: 0x0000000000000000
  rip: 0x0000000106943c13  rfl: 0x0000000000010202  cr2: 0x0000000000000000
Logical CPU: 0

Binary Images:

---omitted--------

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 299
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 19585
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=180.7M resident=88.5M(49%) swapped_out_or_unallocated=92.2M(51%)
Writable regions: Total=915.4M written=786.7M(86%) resident=840.7M(92%) swapped_out=0K(0%) unallocated=74.7M(8%)
 
REGION TYPE                      VIRTUAL
===========                      =======
CG backing stores                  13.5M
CG image                             20K
CG raster data                       96K
CG shared images                    256K
CoreImage                             4K
CoreServices                       2560K
MALLOC                            871.0M
MALLOC guard page                    48K
Memory tag=240                        4K
Memory tag=242                       12K
Memory tag=243                        4K
OpenCL                                8K
SQLite page cache                    96K
STACK GUARD                        56.0M
Stack                              13.1M
VM_ALLOCATE                        16.2M
__DATA                             13.9M
__IMAGE                             528K
__LINKEDIT                         62.1M
__TEXT                            118.6M
__UNICODE                           544K
mapped file                         1.9G
shared memory                      18.4M
===========                      =======
TOTAL                               3.1G

[etotheipi]

Sorry guys, I dropped out of contact for a while to try to get some coding&development done.  I will get to all of the posts here eventually.   For now, I would just like to post a 0.2 BTC bounty as described in this post.  This bug is holding up the release schedule, and I can't reproduce it reliably. 

Many of you have reported this occurring at some point.  But I still don't have a solid pattern for it.  I have a couple things I think might fix it, but I won't know if I've fixed it unless I can reproduce it!

If you have gotten Armory fully online and can do some testing for me, help me find the pattern and claim the 0.2 BTC!

[etotheipi]

Note, the disappearing tx bug has been found!  Just posted about it in the other thread.  Rapidly getting closer to a releasable piece of software!

[Zomdifros]

I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.

However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.

[etotheipi]

I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.

However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.

Zomdifros,

Perfect, send me a log file!  When you click a button and it doesn't do anything, it's dumping an error message in the log file every time.  Usually those are very stupid errors and quick fixes.  "File"->"Export Log File" and we'll give you a 1x bounty if there's a real, actionable error in there.

[Zomdifros]

I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.

However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.

Zomdifros,

Perfect, send me a log file!  When you click a button and it doesn't do anything, it's dumping an error message in the log file every time.  Usually those are very stupid errors and quick fixes.  "File"->"Export Log File" and we'll give you a 1x bounty if there's a real, actionable error in there.

Sure, just sent you an email with the log file!

[scomil]

Hi,

Warning - this might be a user error:) - if so, feel free to verbally slap me.

I have downloaded and installed the Armory client. Before committing any funds I wanted to try - Test a Paper Backup. Trouble is, when I press the test backup button, after entering the full root key, nothing happens.

Many thanks & good work on this fantastic client.

[etotheipi]

Hi,

Warning - this might be a user error:) - if so, feel free to verbally slap me.

I have downloaded and installed the Armory client. Before committing any funds I wanted to try - Test a Paper Backup. Trouble is, when I press the test backup button, after entering the full root key, nothing happens.

Many thanks & good work on this fantastic client.

Send me a log file.  support@bitcoinarmory.com  .  I can usually identify these things pretty quickly!

[elbandi]

Hi,

Latest Armory on windows xp sp3.
I use the windows as normal (regular) user without admin/poweruser permissions (=no write access to c:\windows or c:\program files directory)

i try to start Armory, i got this:
http://imgur.com/tUQNq9n

i think logs and settings should be written to appdata.

Elbandi

[etotheipi]

Code:

(WARNING) ArmoryQt.py:1391 - Tried to start bitcoind, but satoshi already running
(WARNING) ArmoryQt.py:932 - running from: C:\Users\vbox\BitcoinArmory\ArmoryStandalone\ArmoryQt.exe, key: "C:\Users\vbox\BitcoinArmory\ArmoryStandalone\ArmoryQt.exe" %1
(WARNING) ArmoryQt.py:1013 - app dir: C:\Users\vbox\BitcoinArmory\ArmoryStandalone
(ERROR) armoryengine.pyc:13135 - Resetting BDM and all wallets
Traceback (most recent call last):
  File "ArmoryQt.py", line 22, in <module>
  File "psutil\__init__.pyc", line 85, in <module>
  File "psutil\_psmswindows.pyc", line 15, in <module>
  File "_psutil_mswindows.pyc", line 12, in <module>
  File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.

Unfortunately, the new version doesn't support Windows XP, yet.  Goatpig has a solution, but it looks like it would complicate this release (0.90-beta), so it's being reserved for the release after this one (0.91-beta).

[tc23emp]

Code:

2013-11-23 04:33 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 6808, in broadTx
  File "ArmoryQt.py", line 2619, in broadcastTransaction
  File "armoryengine.pyc", line 10793, in sendTx
ConnectionError: Connection to localhost DNE.

If maxConnections is set in bitcoind, this error shows in the logs after you enter your password to complete sending bitcoins. The GUI doesn't show any error; it just leaves the send window open (password dialog closes itself). Obviously, the bitcoins never send (nothing pending).

Another wierd thing is also happening. While the databases are still being created or transactions are being scanned, the message "You just clicked a bitcoin: link..." pops up when you open armory from the systray. I've never actually clicked on a bitcoin: link, but the program thinks I did. It says to try again when Armory is online. This has never happened when armory is actually online.

Also, not sure if this is the place, but could you consider adding a command-line switch to start armory in the systray (if the systray option is already enabled as well).

[elbandi]

Hi,

I try to run Armory on a lucid x64. It's crashing, here is the stdout and stderr:
stdout: http://pastebin.com/ca9LML95
stderr: http://pastebin.com/EhQ4uapi

i already run bitcoin-qt -rescan, so blockchain sould be good.

What sould i do?

Elbandi

[simonvrouwe]

I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.

However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.

I have the exact same issue, running Armory 0.90beta on kubuntu 12.04. When I raise the fee to 0.0001 and wait a few minutes the transaction (list) gets through.

[devthedev]

Is there any ETA about when the Bounty will be paid out?

[etotheipi]

My apologies guys.  I've been swamped with the new release, and preparing for the conference next week.  I'll spend some time today going through and tallying up how many people get bounties.  If you believe you get a bounty, please PM me your address and let me know if you are okay with a single outgoing payment with all recipients at once.  I prefer to reduce blockchain bloat, but I'm also okay with it if privacy is important to you.

[devthedev]

My apologies guys.  I've been swamped with the new release, and preparing for the conference next week.  I'll spend some time today going through and tallying up how many people get bounties.  If you believe you get a bounty, please PM me your address and let me know if you are okay with a single outgoing payment with all recipients at once.  I prefer to reduce blockchain bloat, but I'm also okay with it if privacy is important to you.

No problem, I was just curious, no rush. PMed

[etotheipi]

I just updated the list on the first post.   I think that covers everything.  I have basically ignored any OSX issues since that was completely hosed.  Hopefully we'll get an OSX build going, after the conference.

If you are on the list, please PM me with payment address and specify if you are okay with me sending one transaction with multiple outputs to everyone receiving a bounty. 

BTW:  a lot of these bugs will actually be fixed in 0.91-beta.  I didn't perceive most of them to be showstoppers for 0.90.  It was the showstopping bugs that I was looking for that would make for an embarrassing release...

Thanks everyone for helping out!  If you continue bug-hunting in 0.90, and find new bugs, feel free to post here and I'll honor the bounty up to the limit I originally specified. 

[devthedev]

I just updated the list on the first post.   I think that covers everything.  I have basically ignored any OSX issues since that was completely hosed.  Hopefully we'll get an OSX build going, after the conference.

If you are on the list, please PM me with payment address and specify if you are okay with me sending one transaction with multiple outputs to everyone receiving a bounty. 

BTW:  a lot of these bugs will actually be fixed in 0.91-beta.  I didn't perceive most of them to be showstoppers for 0.90.  It was the showstopping bugs that I was looking for that would make for an embarrassing release...

Thanks everyone for helping out!  If you continue bug-hunting in 0.90, and find new bugs, feel free to post here and I'll honor the bounty up to the limit I originally specified. 

No problem, I had fun!

[jyyst]

I just updated the list on the first post.   I think that covers everything.  I have basically ignored any OSX issues since that was completely hosed.  Hopefully we'll get an OSX build going, after the conference.

If you are on the list, please PM me with payment address and specify if you are okay with me sending one transaction with multiple outputs to everyone receiving a bounty. 

BTW:  a lot of these bugs will actually be fixed in 0.91-beta.  I didn't perceive most of them to be showstoppers for 0.90.  It was the showstopping bugs that I was looking for that would make for an embarrassing release...

Thanks everyone for helping out!  If you continue bug-hunting in 0.90, and find new bugs, feel free to post here and I'll honor the bounty up to the limit I originally specified. 

It is not a problem for me too. My BTC address: 1Nbu8kh1Y6ti98BazN6KeanYvkUKwvwtd2 . When are you going to fix the error that I reported (crash with a lot of addresses)?

[cverity]

I installed Armory on a Windows 7 work PC with the intention of importing watch-only wallets.

I couldn't get Armory to go into online mode.  Eventually I figured out what was happening.  I log into my PC as a domain user, and my home directory is c:\users\<domain user>.<domain name\ - My USERPROFILE environment variable is set correctly, and bitcoin-qt and bitcoind read from the correct c:\users\<domain user>.<domain name> directory, and my permissions on that directory only give my domain user account access.

I finally discovered, that anytime I launched Armory, the permissions on bitcoin.conf would get changed.  My domain user's permissions would be removed, and replaced by permissions for my local user. As a result, when Armory tried to launch bitcoind in the background, it was unable to read the file and failed to launch.

This only happens when I launch Armory. I does not happen when I run bitcoin-qt or bitcoind independently.

If I tell Armory to not run bitcoin in the background, and I run it myself, then everything worked fine.

However, I did discover a solution. I modified the permissions for bitcoin.conf, by adding my domain user back in with full permissions, and removing permission for the local user to delete the file or modify its permissions.  Armory is now able to go online just fine.

[cverity]

Not so much a bug, but the Transaction Fee tooltip says:

..."for less than $0.01 USD and helps the network"

You might consider rewording this without specifying a USD amount, since with the current USD exchange rate, a .00005 fee is more than $0.01.  Even a relay fee of .00001 is more than $0.01