0.96.1 testing build #4

[goatpig]

Hi. I have used Armory for years, and I really like it.! Thanks for maintaining it
The latest builds (since 0.96, and including this latest 0.96.02 test build), do not output the comments when the transaction lists are exported via the "Export Transactions" to CSV menu.
For instance:
2014-Apr-21 12:58pm,9eb...,738339,3AznXg8eo,MyWallet (Watch),0.01,,,        0.01000000,        0.01000000,""

In previous versions, this was output as:
2014-Apr-21 12:58pm,9eb...,738339,3AznXg8eo,MyWallet (Watch),0.01,,,        0.01000000,        0.01000000,"InputTest"

So you can see that the comment (which is still visible in the Armory UI) is missing from the Exported Transactions.
Can you advise / fix? I really need this comment information to maintain my records of transactions...
Thanks Dave

I can't reproduce. Are the missing comments address or tx comments? Address comments are created in the wallet properties dialog, tx comments are made  in the main ledger.

[Carlton Banks]

In this case, the build target is OS X 10.7. Until I get the go-ahead to switch it to 10.8 (I believe goatpig wanted to ensure that older Mac users could get a version of Armory with SegWit support)

I'm fairly sure that 10.7 won't work with Core 13.0 and higher, as 10.7 doesn't have C++11.

[gangtraet]

In this case, the build target is OS X 10.7. Until I get the go-ahead to switch it to 10.8 (I believe goatpig wanted to ensure that older Mac users could get a version of Armory with SegWit support), users will have to swizzle the bits manually. The easiest thing to do is to go into the OS X build script and change the target version from 10.7 to 10.8. That should fix your issue.

I tried it, unfortunately the build still fails the same way.

I found this in the build log:

Code:

********************************************************************************
2017-Jun-11 09:23pm
Executing: "make DESTDIR="/Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py" install -j4 2>&1 | tee -a /Users/****/development/BitcoinArmory/osxbuild/build-app.log.txt"
Executing from: ".."
Making install in cppForSwig
Making install in lmdb
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
Making install in fcgi
make[2]: *** No rule to make target `install'.  Stop.
make[1]: *** [install-recursive] Error 1
make: *** [install-recursive] Error 1
Finished executing: "make DESTDIR="/Users/****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py" install -j4 2>&1 | tee -a /Users/****/development/BitcoinArmory/osxbuild/build-app.log.txt"
Finished executing from: ".."
********************************************************************************

and this a bit later:

Code:

********************************************************************************
2017-Jun-11 09:23pm
Executing: "patch -p0 < /Users/****/development/BitcoinArmory/osxbuild/qmake_LFLAGS.patch 2>&1 | tee -a /Users/****/development/BitcoinArmory/osxbuild/build-app.log.txt"
Executing from: "/Users/****/development/BitcoinArmory/osxbuild/objc_armory"
patching file ./Makefile
Hunk #1 FAILED at 15.
1 out of 1 hunk FAILED -- saving rejects to file ./Makefile.rej
Finished executing: "patch -p0 < /Users/****/development/BitcoinArmory/osxbuild/qmake_LFLAGS.patch 2>&1 | tee -a /Users/****/development/BitcoinArmory/osxbuild/build-app.log.txt"
Finished executing from: "/Users/****/development/BitcoinArmory/osxbuild/objc_armory"
********************************************************************************

[droark]

In this case, the build target is OS X 10.7. Until I get the go-ahead to switch it to 10.8 (I believe goatpig wanted to ensure that older Mac users could get a version of Armory with SegWit support), users will have to swizzle the bits manually. The easiest thing to do is to go into the OS X build script and change the target version from 10.7 to 10.8. That should fix your issue.

I tried it, unfortunately the build still fails the same way.

Try doing this manually in the OS X root directory.

Code:

git submodule init
dit submodule update

I don't know why this isn't done automatically but it seems to be required on OS X at least.

[gangtraet]

Code:

git submodule init
dit submodule update

I don't know why this isn't done automatically but it seems to be required on OS X at least.

Should have worked that one out myself   I really like git, but the submodule stuff is so user-unfriendly that I decided to do something else in one of my own projects (a bit more work for me, but people who clone it have a chance).

I also pulled from the testing branch, probably shouldn't have done that, as I get a crash much earlier:

Code:

********************************************************************************
Unpacked: /Users/****/development/BitcoinArmory/osxbuild/workspace/downloads/Python-2.7.13.tar.xz
  /Users/****/development/BitcoinArmory/osxbuild/workspace/unpackandbuild/.DS_Store
  /Users/****/development/BitcoinArmory/osxbuild/workspace/unpackandbuild/Python-2.7.13
*** ERROR:  tarfile unpacked more than one object! ***
Modify Python modules setup files.
OpenSSL path = /usr/local/opt/openssl
Traceback (most recent call last):
  File "build-app.py", line 834, in <module>
    main()
  File "build-app.py", line 142, in main
    compile_python()
  File "build-app.py", line 450, in compile_python
    modSetupFile = path.join(bldPath, 'Modules/Setup.dist')
  File "/usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/posixpath.py", line 70, in join
    elif path == '' or path.endswith('/'):
AttributeError: 'list' object has no attribute 'endswith'

But you probably should not waste time helping me with this.  Goatpig has released 0.96.0.2 last week with an OSX build (thank you !!!), I will try that tonight.

[goatpig]

Should have worked that one out myself   I really like git, but the submodule stuff is so user-unfriendly that I decided to do something else in one of my own projects (a bit more work for me, but people who clone it have a chance).

That turned out to be much worse than what I had expected. I'll prolly move to git subtree instead.

[gangtraet]

I have now tested the new testing build on macOS X 10.12.5.

The good news is that it runs, and the few features I have tested work as expected.

The bad news is that you are going to get a lot of posts from frustrated users who cannot start the app: 
It looks like if you unzip the application, you cannot run it until you have manually moved the app bundle to another folder !

I am 99% sure it is App Translocation, a new security feature in macOS which causes this as a side effect.  App Translocation prevents some forms of attacks to some type of apps by copying the entire app into a disk image which is then made read-only.  Then the app is executed from within this disk image.  Once an app is moved with the Finder (but not with mv) then App Translocation is disabled for the app, since moving it prevents the kind of attacks App Translocation was designed to protect against.

So if you do not move Armory, it is executed from within a read-only disk image, in my case from this path:

Code:

/private/var/folders/cq/5k4g7j_j5q3crgmh_glgp8yr0000gn/T/AppTranslocation/75F2CD25-05E9-4AC8-A15C-98AEE371C58F/d/Armory.app/Contents/MacOS

Why would that matter?  After all, Armory does not care from where it is executed?  Well, the problem is that this disk image is read-only, and the first time Armory starts it makes a softlink inside itself.  That fails if the disk image is read-only, and then the Armory startup script cannot execute Python!

Code:

# OS X has a quirk. For whatever reasons, if you execute Python from a different
# location than the location of what actually gets executed when you run Armory,
# the menu bar calls Armory "Python". However, if you symlink Python and run the
# symlink from the execution directory, the app name from Info.plist is used.
# Also, the link should be here so that the link works wherever this is
# executed, and not just on the build machine.
ln -sf "${FRDIR}/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python" "${DIRNAME}/Python"

# Assume all args are meant for Armory. Assuming otherwise, for shell scripts
# at least, it horribly painful.
exec "${DIRNAME}/Python" "${ARMORYDIR}/ArmoryQt.py" "$@"

Symptoms:

• If you download Armory as a zip file, unpack it, and run it by double-clicking Armory.app, it fails to start
• If you drag Armory to /Applications (or anywhere else for that matter), it suddenly works (since this disables App Translocation).
• Or, if you start it on the command line in the original location by typing /path/to/Armory.app/Contents/MacOS/Armory, then it is run without AppTranslocation, and works.  Now the softlink has been made, and double-clicking on Armory.app will now work (since although App Translocation is still in place, the softlink was made in the original App)

Info about App Translocation:  http://lapcatsoftware.com/articles/app-translocation.html
and more detailed, including a similar case to what we see with Armory: https://www.synack.com/2016/12/16/untranslocating-apps/

Recommendation: Since the softlink inside the app is internal, it could be made when the app is build instead of as a workaround when running it.  Then App Translocation will not matter.

[gangtraet]

One small usage problem.  If I exit Armory, I need to wait a minute or so before starting it again, otherwise it fails to start.  It is not ArmoryDB running, it has already stopped.  I see this in the log:

Code:

2017-06-12 20:59:38 (INFO) -- ArmoryUtils.py:1689 - C++ block utilities loaded successfully
2017-06-12 20:59:38 (INFO) -- ArmoryUtils.py:3587 - Using settings file: /Users/****/Library/Application Support/Armory/ArmorySettings.txt
2017-06-12 20:59:38 (ERROR) -- ArmoryUtils.py:3744 - Unsupported language  specified. Defaulting to English (en)
2017-06-12 20:59:38 (INFO) -- ArmoryUtils.py:3747 - Using Language: en
2017-06-12 20:59:38 (INFO) -- BDM.py:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-06-12 20:59:38 (INFO) -- BDM.py:366 - Blockchain operations will happen in the background.  
2017-06-12 20:59:38 (INFO) -- BDM.py:367 - Devs: check TheBDM.getState() before asking for data.
2017-06-12 20:59:38 (INFO) -- BDM.py:368 - Registering addresses during rescans will queue them for 
2017-06-12 20:59:38 (INFO) -- BDM.py:369 - inclusion after the current scan is completed.
2017-06-12 20:59:38 (ERROR) -- ArmoryQt.py:5892 - Socket already in use.  Sent CLI args to existing proc.
2017-06-12 20:59:38 (ERROR) -- ArmoryQt.py:5893 - Exiting...

[goatpig]

That's the process mutex, suggesting the listen socket on the previous client has not been closed yet. You toy with it here, figure out what's going on:

https://github.com/goatpig/BitcoinArmory/blob/testing/cppForSwig/SwigClient.cpp#L1065

[creamers]

Bug ?

I have two wallets, one native and one cold wallet.
When Filter is set to "all wallets"  and I double click on Comments in that particular colomn, paste the text and press oke , the Filter will jump to My Wallets automatically....

imo it should stay at the same filter settings.

[goatpig]

Post armorylog.txt

[creamers]

I cleared the log, then started armory and did what I described earlier. (add a comment and then the filter switches to my wallet when it was set on all wallets)

https://pastebin.com/Gxqr5nZ6

I think this is some sort of gui bug thingy ? :   http://imgur.com/a/ECgRQ

[goatpig]

Bumping for the new testing builds.

[creamers]

Nice! ( https://github.com/goatpig/BitcoinArmory/commit/eb826b671155eb57fe7271c8d140431ebe8b8bbc )
Will test some more.

*EDIT

First time after installation after every startup and changing the comments it flipped back. The second edit it didnt flip back to my wallet and stayed at all wallets.

[goatpig]

If the bug is still there, you gonna have to try and narrow it down. It didn't happen anymore in my testing after the fix.

[creamers]

Found the problem.

I have two wallets. One watch only wallet en one native wallet.
When I open Armory it defaults to "My Wallets" showing both wallets !! (Think this is already wrong as it should not show the WatchOnly wallet.)
Changing a comment activates the Filter, meaning, it then becomes active and the WatchOnly wallet disappears because it doesnt belong in the filter view My Wallets.

It's either case, the watch only wallet should be visible in 'my wallets'   OR the filter should become active at  startup and not only when comments are changed.

I think it should be set to All Wallets at startup showing all wallets. Problem solved

Hope it helps, otherwise let me know.

(ps, I noticed alot more crashes at closing but will investigate / narrow it down)

[creamers]

see previous post about Filter.

Now about the crashes...it seems to crash while it was running oke....now happened several times.

Code:

2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1135 - C++ block utilities loaded successfully
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1252 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1253 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1254 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1255 - ************************************************************
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1256 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=c:\Armory Database --satoshi-datadir=c:\Bitcoin Core Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1257 - ************************************************************
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1258 - Loading Armory Engine:
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1259 -    Armory Version        : 0.96.0.3
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1260 -    Armory Build:         : 1a126dd6ec
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1261 -    PyBtcWallet  Version  : 1.35
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1262 - Detected Operating system: Windows
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1263 -    OS Variant            : 2008ServerR2-6.1.7601-SP1-Multiprocessor Free
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1264 -    User home-directory   : C:\Users\Administrator\AppData\Roaming
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1265 -    Satoshi BTC directory : c:\Bitcoin Core Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1266 -    Armory home dir       : c:\Armory Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1267 - Detected System Specs    : 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1268 -    Total Available RAM   : 3.87 GB
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1269 -    CPU ID string         : AMD64 Family 16 Model 6 Stepping 3, AuthenticAMD
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1270 -    Number of CPU cores   : 2 cores
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1271 -    System is 64-bit      : True
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1272 -    Preferred Encoding    : cp1252
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1273 -    Machine Arch          : amd64
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1274 -    Available HDD (ARM)   : 657 GB
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1275 -    Available HDD (BTC)   : 657 GB
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1276 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1277 - Network Name: Main Network
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1278 - Satoshi Port: 8333
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1279 - Do wlt check: True
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1280 - Named options/arguments to armoryengine.py:
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     thread_count    : -1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rescan          : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     ignoreAllZC     : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rescanBalance   : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     disableModules  : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     port            : None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     interport       : 8223
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     coverageOutputDir: None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     forceWalletCheck: False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     regtest         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rebuild         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     nettimeout      : 2
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     datadir         : c:\Armory Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     clearMempool    : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     offline         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     armoryDBDir     : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     armorydb_port   : 9001
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     satoshiPort     : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     useTorSettings  : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     netlog          : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     keypool         : 100
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     coverageInclude : None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     forceOnline     : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     redownload      : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rpcBindAddr     : 127.0.0.1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     armorydb_ip     : 127.0.0.1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     multisigFile    : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     ram_usage       : -1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     mtdebug         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     logDisable      : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     settingsPath    : c:\Armory Database\ArmorySettings.txt
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     language        : en
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     db_type         : DB_FULL
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     doDebug         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     enableDetSign   : True
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     disableConfPermis: False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     testnet         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rpcport         : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     satoshiHome     : c:\Bitcoin Core Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     satoshiRpcport  : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     logFile         : c:\Armory Database\ArmoryQt.exe.log.txt
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     verbosity       : None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1283 - Other arguments:
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1689 - C++ block utilities loaded successfully
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:3587 - Using settings file: c:\Armory Database\ArmorySettings.txt
2017-06-14 19:53:13 (ERROR) -- ArmoryUtils.pyc:3744 - Unsupported language  specified. Defaulting to English (en)
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:3747 - Using Language: en
2017-06-14 19:53:13 (INFO) -- BDM.pyc:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-06-14 19:53:13 (INFO) -- BDM.pyc:366 - Blockchain operations will happen in the background.  
2017-06-14 19:53:13 (INFO) -- BDM.pyc:367 - Devs: check TheBDM.getState() before asking for data.
2017-06-14 19:53:13 (INFO) -- BDM.pyc:368 - Registering addresses during rescans will queue them for 
2017-06-14 19:53:13 (INFO) -- BDM.pyc:369 - inclusion after the current scan is completed.
2017-06-14 19:53:14 (INFO) -- ArmoryUtils.pyc:3587 - Using settings file: c:\Armory Database\ArmorySettings.txt
2017-06-14 19:53:14 (INFO) -- ArmoryQt.py:2045 - loadWalletsAndSettings
2017-06-14 19:53:14 (INFO) -- ArmoryQt.py:2105 - Loading wallets...
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:2170 - Number of wallets read in: 2
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:2175 -    Wallet (7GuJwatF):    "BurtsWallet (Watch)             "   (No Encryption)
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:2175 -    Wallet (DW1EHSXZ):    "Restored - DW1EHSXZ             "   (Encrypted)
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1386 - setupUriRegistration
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1454 - Armory already registered for current user.  Done!
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:560 - Usermode: Advanced
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1682 - Changing usermode:
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1683 -    From: Advanced
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1691 -      To: Advanced
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1820 - startBitcoindIfNecessary
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1856 - setSatoshiPaths
2017-06-14 19:53:17 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2017-06-14 19:53:17 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2017-06-14 19:53:17 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-06-14 19:53:17 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-06-14 19:53:18 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=c:\\Bitcoin Core Database']
2017-06-14 19:53:18 (INFO) -- SDM.pyc:442 - PID of bitcoind: 17984
2017-06-14 19:53:18 (INFO) -- SDM.pyc:443 - PID of armory:   4924
2017-06-14 19:53:18 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['.\\guardian.exe', '4924', '17984']
2017-06-14 19:53:21 (INFO) -- ArmoryQt.py:1856 - setSatoshiPaths
2017-06-14 19:53:21 (WARNING) -- SDM.pyc:395 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="c:\Bitcoin Core Database\blocks" --datadir="c:\Armory Database" --dbdir="c:\Armory Database\databases"
2017-06-14 19:53:21 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="c:\\Bitcoin Core Database\\blocks"', '--datadir="c:\\Armory Database"', u'--dbdir="c:\\Armory Database\\databases"']
2017-06-14 19:53:23 (INFO) -- ArmoryQt.py:1808 - Connecting on port 50655
2017-06-14 19:53:23 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-14 19:53:24 (INFO) -- ArmoryQt.py:1890 - loadBlockchainIfNecessary
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:26 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:27 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:28 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:29 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:30 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:31 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:32 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:33 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:45 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:48 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:48 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:49 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:49 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:54:15 (WARNING) -- ArmoryQt.py:4078 - Called updateSyncProgress while not sync'ing
2017-06-14 20:00:38 (INFO) -- ArmoryQt.py:4914 - New Block! : 471263
2017-06-14 20:00:38 (INFO) -- ArmoryQt.py:4922 - Current block number: 471263
2017-06-14 20:13:33 (INFO) -- ArmoryQt.py:4914 - New Block! : 471264
2017-06-14 20:13:33 (INFO) -- ArmoryQt.py:4922 - Current block number: 471264
2017-06-14 20:19:23 (INFO) -- ArmoryQt.py:4914 - New Block! : 471265
2017-06-14 20:19:23 (INFO) -- ArmoryQt.py:4922 - Current block number: 471265
2017-06-14 20:23:18 (WARNING) -- ArmoryQt.py:4078 - Called updateSyncProgress while not sync'ing

Code:

-WARN  - 20:22:40.241: (..\BDM_supportClasses.cpp:1898) running 2285 zc parser threads
-WARN  - 20:22:40.241: (..\BDM_supportClasses.cpp:1898) running 2290 zc parser threads
-WARN  - 20:22:53.924: (..\BDM_supportClasses.cpp:1898) running 2295 zc parser threads
-WARN  - 20:22:53.924: (..\BDM_supportClasses.cpp:1898) running 2300 zc parser threads
-WARN  - 20:22:53.939: (..\BDM_supportClasses.cpp:1898) running 2305 zc parser threads
-WARN  - 20:22:53.939: (..\BDM_supportClasses.cpp:1898) running 2310 zc parser threads
-WARN  - 20:22:53.955: (..\BDM_supportClasses.cpp:1898) running 2315 zc parser threads
-ERROR - 20:23:18.024: (..\SocketObject.cpp:285--ERROR - 20:23:18.040: (WARN  - ..\SocketObject.cpp:134) POLLERR error in readFromSocketThread
20:23:18.040) POLLERR in writeToSocket
: (..\BDM_supportClasses.cpp:1898) running 2320 zc parser threads
-WARN  - 20:23:18.055: (..\BDM_supportClasses.cpp:1898) running 2325 zc parser threads
-WARN  - 20:23:18.071: (..\BDM_supportClasses.cpp:1898) running 2330 zc parser threads
-WARN  - 20:23:18.071: (..\BDM_supportClasses.cpp:1898) running 2335 zc parser threads
-ERROR - 20:23:18.087: (..\SocketObject.cpp:134) POLLERR in writeToSocket
-ERROR - 20:23:18.087: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.102: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-WARN  - 20:23:18.102: (..\BDM_supportClasses.cpp:1898) running 2340 zc parser threads
-ERROR - 20:23:18.133: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.133: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-WARN  - 20:23:18.149: (..\BDM_supportClasses.cpp-ERROR - :189820:23:18.149: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038) running 2345
 zc parser threads-ERROR - 
20:23:18.165: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.180: (..\SocketObject.cpp:126-WARN  - ) 20:23:18.196: (..\BDM_supportClasses.cpp:1898poll() error in writeToSocket: 10038
) running 2350 zc parser threads
-ERROR - 20:23:18.196: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.211: (..\SocketObject.cpp:126-ERROR - ) 20:23:18.211: (..\BitcoinP2P.cpp:1027poll() error in writeToSocket: 10038) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread

-ERROR - -INFO  - 20:23:18.227: (..\SocketObject.cpp:12620:23:18.227: (..\BitcoinP2P.cpp:969) ) Disconnected from Bitcoin node
poll() error in writeToSocket: 10038

[goatpig]

Code:

running 2340 zc parser threads

This is a relevant symptom. How large is your node's mempool? Anything worth of note getting to that point? Let the Armory run for a few hours, does it get to that point?

(Think this is already wrong as it should not show the WatchOnly wallet.)
...
It's either case, the watch only wallet should be visible in 'my wallets'

Which one is it? WO's can be considered your wallet as long as you specify that in the ownership field. They are not by default however.

[idoB]

I can confirm the bug preventing use of fragmented backups is fixed. THANKS!

On the down side, the bug exporting key list reported here:
https://bitcointalk.org/index.php?topic=1957569.0
still there in 96.1.0.3 (same error in log).

Log:

Code:

 (ERROR) -- Traceback (most recent call last):
  File "ui\WalletFrames.pyc", line 1136, in clickedDoIt
  File "qtdialogs.pyc", line 4947, in __init__
  File "qtdialogs.pyc", line 5006, in rewriteList
  File "CppBlockUtils.pyc", line 4035, in getAddrObjByIndex
RuntimeError: invalid asset index

[creamers]

Code:

running 2340 zc parser threads

This is a relevant symptom. How large is your node's mempool? Anything worth of note getting to that point? Let the Armory run for a few hours, does it get to that point?

Taskmanager:
https://s16.postimg.org/6gctny42t/taskmanager.png
It's running fine untill it crashes. .2 test version didnt do that. Cleared the log files and started it again. Here they are:

armory log:
https://pastebin.com/TiWpt0yr

dblog:
https://pastebin.com/DFJ7TrBc

Which one is it? WO's can be considered your wallet as long as you specify that in the ownership field. They are not by default however.

Let me rephrase, I have two wallets, one mine and one not mine. When I start armory the filter is default to MyWallets setting but it's showing ALL wallets until I change something in the comments fields, then it will show only My Wallets and thus showing one wallet in my case.
(If armory start defaulting to My Wallets then it should only show my wallets and not all of them.)