I imported a watchonlywalllet and now Armory 0.9.12 on Mac OS 10.9.3 keeps crashing on startup. Cant use it, what can I do? Switch back to 0.9.11 ?!

-INFO  - 1402126750: (BlockUtils.cpp:4527) Starting scan from block height: 0
-ERROR - 1402126750: (leveldb_wrapper.cpp:1787) Invalid txIndex at height 0 index 269
-ERROR - 1402126750: (StoredBlockObj.cpp:1082) Cannot get tx copy, because don't have full StoredTx!

1) Thank you very much! I really need this under OS X :/ Do I have to wait for the next version or will there be a work around?

2) Is it equally safe to use qr codes instead of typing the transaction signing data with my keyboard into the offline computer? Are there any good linux qr code generators that can create codes from a file?

Hi,

1) Which is the recommend version for setting up a new (offline) wallet?
0.91.2 for creating & broadcasting and 0.90 for the offline one? I am afraid of the recent bugs.

2) I don't want to transfer the created & signed transactions by usb (ultra paranoid ). After I move the armory offline bundle to the offline machine and back upped the wallet I never want to have a cd/usb stick in the offline computer again.How large is the average transaction and how long do you think will it take to type it by hand? if it can be done in 10minutes I am totally okay with that.

3) Is the torrent blockchain downloader included in all new armory versions (linux, windows, mac os)? I am not sure if it works on Mac OS. I started Armory, than bitcoin-qt. As far I can tell it does download the blockchain only with bitcoin-qt.

Thanks!

Today I was facing a strange bug.

Recently I moved all my funds from my old offline wallet to a new one. Yesterday I installed Armory on a new machine and reimported my new offline watch only wallet and the old one, too. After armory has rebuild and scanned the blockchain the balance of my old wallet was zero and all my funds are in the new one - exactly as expected.

I was glad Armory finished all the blockchain building&scanning and wanted to shut down my ubuntu machine. But my Armory GUI did not want to close immediately and my Ubuntu said something like "Cannot shutdown because armory is still running.. Force shutdown?". I decided to wait one more minute but this process did not complete and I finally forced the shutdown.

Today I started Armory again and whooo - my old wallet balance says that this wallet has some coins! I checked the transaction log but there were not any new transactions to this wallet. So I tried to initiate a test transaction to check if I really own these coins. After broadcasting it Armory came up with an error msg "Transaction may have not been broadcasted/may not appear in the blockchain". Okay, I think I really don't own this Coins anymore and there is a database mixup because I forced Armory to shutdown.

Now I am rescanning the transaction history and will report what happens. Or shall I rather "rebuild & rescan" the database?

What's the difference between rebuild&rescan? Does rebuild mean "Download the blockchain again" ?

2014-03-14 00:41 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2014-03-14 00:41 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2014-03-14 00:41 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2014-03-14 00:41 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2014-03-14 00:41 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2014-03-14 00:41 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2014-03-14 00:41 (INFO) -- ArmoryQt.py:4465 - Dashboard switched to fully-online mode
2014-03-14 00:41 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-14 00:41 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Online"
2014-03-14 00:41 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-14 00:41 (INFO) -- ArmoryQt.py:4465 - Dashboard switched to fully-online mode
2014-03-14 00:41 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-14 00:41 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Online"
2014-03-14 00:41 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-14 00:41 (INFO) -- ArmoryQt.py:1913 - Syncing wallet: WALLET1
2014-03-14 00:41 (INFO) -- ArmoryQt.py:1913 - Syncing wallet: WALLET2
2014-03-14 00:41 (INFO) -- ArmoryQt.py:1913 - Syncing wallet: WALLET3
2014-03-14 00:41 (INFO) -- ArmoryQt.py:1925 - Current block number: 290451
2014-03-14 00:53 (INFO) -- ArmoryQt.py:4465 - Dashboard switched to fully-online mode
2014-03-14 00:53 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-14 00:53 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Online"
2014-03-14 00:53 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-14 00:53 (INFO) -- ArmoryQt.py:4465 - Dashboard switched to fully-online mode
2014-03-14 00:53 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-03-14 00:53 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Online"
2014-03-14 00:53 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-03-14 00:53 (INFO) -- ArmoryQt.py:4781 - New Block! : 290452
2014-03-14 00:53 (INFO) -- ArmoryQt.py:4805 - Current block number: 290452
2014-03-14 00:53 (INFO) -- ArmoryQt.py:4982 - BDM is safe for clean shutdown
2014-03-14 00:53 (INFO) -- armoryengine.py:13435 - Shutdown Requested
2014-03-14 00:53 (ERROR) -- armoryengine.py:13216 - Resetting BDM and all wallets
2014-03-14 00:53 (INFO) -- armoryengine.py:13481 - BDM is shutdown.
2014-03-14 00:53 (INFO) -- armoryengine.py:11263 - Called stopBitcoind
2014-03-14 00:53 (WARNING) -- armoryengine.py:661 - Killing process pid=2332
2014-03-14 00:53 (INFO) -- ArmoryQt.py:5010 - Attempting to close the main window!
2014-03-14 00:54 (ERROR) -- armoryengine.py:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-03-14 00:54 (ERROR) -- armoryengine.py:12347 -   getattr   name: hasTxWithHash
2014-03-14 00:54 (ERROR) -- armoryengine.py:12348 - BDM currently doing: Shutdown (47513644)
2014-03-14 00:54 (ERROR) -- armoryengine.py:12349 - Waiting for completion: ID= 56394262
2014-03-14 00:54 (ERROR) -- armoryengine.py:12350 - Direct traceback
2014-03-14 00:54 (ERROR) -- armoryengine.py:12353 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/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
2014-03-14 00:54 (ERROR) -- armoryengine.py:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-03-14 00:54 (ERROR) -- armoryengine.py:12347 -   getattr   name: hasTxWithHash
2014-03-14 00:54 (ERROR) -- armoryengine.py:12348 - BDM currently doing: Shutdown (47513644)
2014-03-14 00:54 (ERROR) -- armoryengine.py:12349 - Waiting for completion: ID= 63415093
2014-03-14 00:54 (ERROR) -- armoryengine.py:12350 - Direct traceback
2014-03-14 00:54 (ERROR) -- armoryengine.py:12353 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/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
2014-03-14 00:54 (ERROR) -- armoryengine.py:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-03-14 00:54 (ERROR) -- armoryengine.py:12347 -   getattr   name: hasTxWithHash
2014-03-14 00:54 (ERROR) -- armoryengine.py:12348 - BDM currently doing: Shutdown (47513644)
2014-03-14 00:54 (ERROR) -- armoryengine.py:12349 - Waiting for completion: ID= 66787172
2014-03-14 00:54 (ERROR) -- armoryengine.py:12350 - Direct traceback
2014-03-14 00:54 (ERROR) -- armoryengine.py:12353 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/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

The last error log block appeared some more times

Update:
Okay, after rescanning the database it shows the (hopefully) correct balance again. I suggest to do a auto-rescan if this error can be tracked.

Just try it by yourself It's working like a charme!

I cannot imagine to use a better wallet than Armory! But as I wrote here https://bitcointalk.org/index.php?topic=503631.0 I am concerned about usb key security (I am ultra paranoid).

Currently the safest method for transferring unsigned&signed transactions is to type it by hand into the computers, right? Now I am asking myself if I can loose my Bitcoins when I have a typo in my transaction plaintext (which is very likely) or does Armory check the file integrity and I just need to check the transaction details Armory brings up to me.

Or should I better wait for your audio transfer feature? (So awesome!)

Hi!

I am concerned about USB key security and not sure if I am ultra paranoid.

Is there any known auto run malware available (For Windows I think yes but linux !? I heard about a nautilus thumbnail exploit)? If yes this malware could infect your USB stick & offline computer that you use to transfer unsigned & signed transactions.

What are the best options to get around this potential security risk? I am aware of the following "solutions":

Hack transactions manually into my computer(s)
Pros:
- Very secure

Contra:
-Very time consuming

QR Code movies
Pros:
- Very secure

Contra:
- Webcam needed
- Not supported yet

Armorys upcoming audio transfer feature
Pros:
- Very secure

Contra:
- Not supported yet / in development

Burn CDs
1 new CD for the unsigned tx, 1 for the signed tx;
Not sure if this is really a security improvement?

What do you think?

Thanks