0.96.4 RC2

[idoB]

Meant to report back on this.
I think Armory is hanging when starting the db process with with popen.

Also verified that there is no need to delete the above two dlls.
To get RC2 running under windows 10, only need to run armorydb separately from the command prompt with the switches in the install-dir armoryqt.exe.log, and then run armoryqt RC2.

Thanks for figuring it out, I'll look into it.

Simple batch file to run Armory on Windows with a single click until the splashscreen hang is resolved. Save below lines to StartArmory.bat:

Code:

cd "C:\Program Files (x86)\Armory\"
start ArmoryDB.exe --db-type=DB_FULL --cookie --satoshi-datadir=f:\bitcoin --datadir=f:\armory --dbdir=f:\armory
start ArmoryQt.exe --datadir=f:\armory
exit

Edit paths to your bitcoin data dir, Armory data dir, Armory Db dir

[droark]

I wanted to create some Segwit addresses to transfer the main BTC holdings. I made various attempts at getting the latest versions working on MacOS (used for watch-wallets and to broadcast offline signed transactions). None of the pre-compiled OSX versions would work with the two Mac High Sierra versions I had locally - 10.12.6 and 10.13.2.

Interesting. It compiles and runs just fine on my 10.13 machine and my VMs. If you have your logs or can recreate this, would you mind opening an issue on GitHub so that I can try to figure out what's going on? I've heard a couple of other people complain. The first guy wasn't really helpful but the second was more sane and saying similar things.

BTW, you don't need the complete Xcode suite. You just need the command line tools. This updated build guide is worth checking if you haven't already.

Thanks!

[5psrWGMxeW]

Just confirming that RC2 hangs forever at splashscreen for me too on windows 10 x64

edit: could you please ditch the faulty captcha on this forum, drives me nuts! or at least try to improve it

[droark]

edit: could you please ditch the faulty captcha on this forum, drives me nuts! or at least try to improve it

You'll have to take that up with Theymos (the admin, last I checked). AFAIK, Goatpig has no control over that.

[idoB]

Bug report: RC2 offline computer does not recognize RC1 transaction?

When trying to sign on an offline signer, running 0.96.3.99 (RC1) a transaction created by an online computer running 0.96.3.991 (RC2), right after loading transaction from file, a red label "Unrecognized!" appears with the following in the log file:

Code:

2018-01-06 08:37:24 (INFO) -- TxFrames.pyc:2267 - Selected transaction file to load: D:/armory_SJFDgm25_.unsigned.tx
2018-01-06 08:37:24 (WARNING) -- Transaction.pyc:1263 - Unexpected nested type for TxIn 16
2018-01-06 08:37:24 (ERROR) -- Transaction.pyc:1289 - Insert list has index too big
2018-01-06 08:37:24 (ERROR) -- Transaction.pyc:1289 - Insert list has index too big

[PhoenixFire]

Bug report: RC2 offline computer does not recognize RC1 transaction?

When trying to sign on an offline signer, running 0.96.3.99 (RC1) a transaction created by an online computer running 0.96.3.991 (RC2), right after loading transaction from file, a red label "Unrecognized!" appears with the following in the log file:

Code:

2018-01-06 08:37:24 (INFO) -- TxFrames.pyc:2267 - Selected transaction file to load: D:/armory_SJFDgm25_.unsigned.tx
2018-01-06 08:37:24 (WARNING) -- Transaction.pyc:1263 - Unexpected nested type for TxIn 16
2018-01-06 08:37:24 (ERROR) -- Transaction.pyc:1289 - Insert list has index too big
2018-01-06 08:37:24 (ERROR) -- Transaction.pyc:1289 - Insert list has index too big

You should be running RC2 on the offline PC as well.

[goatpig]

01d9d0cb000100000000004100000018000004ff0000031f0000000000000000fffffffefffffff e000000000200

What OS is this on? Clearly this part is off:

Code:

fffffffefffffffe

[alomar]

01d9d0cb000100000000004100000018000004ff0000031f0000000000000000fffffffefffffff e000000000200

What OS is this on? Clearly this part is off:

Code:

fffffffefffffffe

Ubuntu 16.04.3 LTS

anything i can do to fix it?

[goatpig]

I figured something out. Wait for the next RC.

[goatpig]

PhoenixFire, idoB: I cannot reproduce your issue on either my setup nor fresh Win7 & Win10 VMs. Are you using the installed version or the .zip standalone? If you are using the installed version, can you try with the .zip?

[alomar]

I figured something out. Wait for the next RC.

you ARE the man.

[PhoenixFire]

PhoenixFire, idoB: I cannot reproduce your issue on either my setup nor fresh Win7 & Win10 VMs. Are you using the installed version or the .zip standalone? If you are using the installed version, can you try with the .zip?

Thanks for nudge towards the zip. So, it seems like something is possibly choking related to passing in the working directory.
Directly running ArmoryQt.exe from either the zip or installer version works perfectly: DB launches and everything works as expected.
Launching from a shortcut hangs - Except if the shortcut's "Start In" field matches the install directory.

Sooo this works fine:

Code:

Target:
"C:\Program Files (x86)\Armory\ArmoryQt.exe"
Start In:
"C:\Program Files (x86)\Armory"

This does not work, and I believe is the default shortcut created by the installer:

Code:

Target:
"C:\Program Files (x86)\Armory\ArmoryQt.exe"
Start In:
"C:\Users\Public\Desktop"

This also does not work:

Code:

Target:
"C:\Program Files (x86)\Armory\ArmoryQt.exe"
Start In:
-Leave blank-

Can't believe it was such a minor thing - but RC1 didn't care about the working directory. Hooray for not really being a code problem?

[idoB]

PhoenixFire, idoB: I cannot reproduce your issue on either my setup nor fresh Win7 & Win10 VMs. Are you using the installed version or the .zip standalone? If you are using the installed version, can you try with the .zip?

Can confirm PhoenixFire finding: It's the shortcut 'Start In' path field that needs to point to Armory install-dir in 0.96.3.991 where it didn't before.

[Armory non geek]

actions report re the update to the friend's computer:

I found the link for Armory 0.96.3.991 at the top of this thread and installed to the friend's Win 10 x 64 computer. 

The load in of 0.96.3991 successfully interfaced and upgraded the 0.96.3 already installed, retaining the watcing only "offline" security status of the wallets already installed (with non correct zero balance indicated for each of the watching only copies of those on line wallets).   

Bitcoin core 0.15.1 had already been installed and synced to itself. 

Once Armory 0.96.3991 was loaded various experiments were attempted:

1) close BC core 0.15.1, and then start 0.96.3991 - result 0.96.3991 continued to not sync to BCcore 0.15.1

2) open core 0.15.1 first and then start 0.96.3991 - same result of 0.96.3991 not syncing to Core 0.15.1

3) open 0.96.3991 first and then attempt to open CoredB 0.15.1 - result 0.15.1 opened and self synced but absent any correlation to 0.96.3991 - also missing any conflict error messages about 0.96.3991 already accessing the CoreDb (ie to the effect that only one copy of CoredB can be open at one time). 

----

Throughout all the above experiments with 0.96.3 and now with 0.96.3991 the watching only wallets are not synced to the CoreDb 0.15.1 and all indicate a zero balance.   

Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1
(after the Bitcoin core 0.15.1 has self synced to itself)? 

Or is there a necessary different procedure of install (as in the older versions 0.93.3 and earlier - where Armory was first installed and then Armory needed to complete the full self sync of the BCcore database) so the wallets will sync and indicate their balances?

Again, TY for your kind assistance. 

[goatpig]

Armory non geek:

Maybe when you'll stop hijacking threads and show some logs someone will help you. Until then, you're not gonna get much assistance.

[Armory non geek]

Apologies for entering my questions to what seemed the most appropriate place thread.
where does one find the log files to post?

I will be pleased to copy them and enter them here.    

TY kindly

[droark]

File -> Export Log File

Upload it to Pastebin or 0bin or Cryptbin or wherever and then post the link here.

[Armory non geek]

File -> Export Log File

Upload it to Pastebin or 0bin or Cryptbin or wherever and then post the link here.

TY droark,

Do I upload from the open Armory command, or upload it from the win 64 exe file (linked at the top of this thread)?  

As a non geek, left brain trained in other fields, I appreciate the help along - so I can assist you folks.

[goatpig]

Make your own thread please.

[Armory non geek]

Make your own thread please.

Done

I very much appreciate the assistance.