Bitcoin Forum>Bitcoin>Project Development
Pages:
Author

Topic: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug] - page 3. (Read 12572 times)

cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 11:41:31 PM
#47
Quote from: etotheipi on November 14, 2013, 10:37:53 PM
  • 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
jbreher
legendary
Activity: 3024
Merit: 1640
lose: unfind ... loose: untight
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 11:14:19 PM
#46
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 
    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
SimonBelmond
full member
Activity: 226
Merit: 100
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 08:25:18 PM
#45
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 - ************************************************************
128bpm
newbie
Activity: 16
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 05:21:34 PM
#44
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:

Quote
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. "
devthedev
legendary
Activity: 1050
Merit: 1004
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 04:04:00 PM
#43
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
SimonBelmond
full member
Activity: 226
Merit: 100
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:38:14 PM
#42
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.
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:32:44 PM
#41
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.
ACVentures
newbie
Activity: 14
Merit: 1
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:17:06 PM
#40
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
hero member
Activity: 616
Merit: 500
Stop using branwallets
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 01:27:35 PM
#39
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
idoB
jr. member
Activity: 70
Merit: 2
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 01:18:45 PM
#38
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.


SimonL
member
Activity: 113
Merit: 11
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 10:58:12 AM
#37
Quote from: etotheipi on November 15, 2013, 12:31:11 PM

Quote from: SimonL on November 15, 2013, 06:10:33 AM
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 
    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.

jyyst
newbie
Activity: 20
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 07:32:08 AM
#36
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 
    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 
    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 
    self.combinedLedger.sort(key=lambda x: currBlk-x[1].getBlockNum()+1, reverse=not sortDir)
TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
(, TypeError("unsupported operand type(s) for -: 'NoneType' and 'int'",), )
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
 
whault
newbie
Activity: 16
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:32:39 AM
#35
Quote from: etotheipi on November 16, 2013, 03:05:13 AM
Quote from: whault on November 16, 2013, 03:00:14 AM

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.
Cyberdyne
hero member
Activity: 630
Merit: 500
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:15:05 AM
#34
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.
etotheipi
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:05:13 AM
#33
Quote from: whault on November 16, 2013, 03:00:14 AM
Quote from: duxZero on November 16, 2013, 01:14:41 AM
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)
whault
newbie
Activity: 16
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 03:00:14 AM
#32
Quote from: duxZero on November 16, 2013, 01:14:41 AM
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.
duxZero
newbie
Activity: 32
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 01:14:41 AM
#31
Didn't even notice, my bad.

But yeah just a suggestion to offer a somewhat more advanced security lockdown to help 'prevent' malware.
etotheipi
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 01:12:00 AM
#30
Quote from: duxZero on November 16, 2013, 01:10:28 AM
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
newbie
Activity: 32
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 01:10:28 AM
#29
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.
whault
newbie
Activity: 16
Merit: 0
Re: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]
November 16, 2013, 12:42:16 AM
#28
Quote from: duxZero on November 15, 2013, 10:44:40 PM
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.
Pages:
Bitcoin Forum>Bitcoin>Project Development
Jump to: