Armory 0.96 third testing builds | Bitcointalksearch.org

Mr.Vice

member

Activity: 96

Merit: 10

Quote from: goatpig on May 01, 2017, 08:33:37 AM

Will fix the simulfund issue for 0.96.1

Nice, thx goatpig ;-)
But anyway this build is running very stable! Didn't see any major issues apart from the before mentioned, but you can still fund the lockbox by just copying the address' public key by openening the wallet properties in expert mode.

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Will fix the simulfund issue for 0.96.1

Mr.Vice

member

Activity: 96

Merit: 10

Quote from: achow101 on May 01, 2017, 08:17:37 AM

Quote from: Mr.Vice on May 01, 2017, 06:47:29 AM

There is a translation in the desciption of the wallet security settings missing. Where it says "Encryped" it should be in German "Verschlüsselt". :-)

Not everything has been translated yet, and some translations seem to be broken (particularly with the Secureprint strings because of unicode). If there are no translations for a string, it will just default to the English strings.

Okay, got it! Another more "urgent" issue I encountered is regarding to multi-sig (MultiSig>FUND>Fund from Wallet). When I use the fund from wallet option the usual warning of simulfund prompts up, but after pressing ok nothing happens.

Code:

2017-05-01 15:09 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1134 - C++ block utilities loaded successfully
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1251 -
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1252 -
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1253 -
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1254 - ************************************************************
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1255 - Invoked: C:\Program Files\Armory\ArmoryQt.exe
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1256 - ************************************************************
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1257 - Loading Armory Engine:
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1258 - Armory Version : 0.95.99.3
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1259 - Armory Build: : 025e0cda7b
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1260 - PyBtcWallet Version : 1.35
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1261 - Detected Operating system: Windows
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1262 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1263 - User home-directory : C:\***\AppData\Roaming
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1264 - Satoshi BTC directory : C:\Users\***\AppData\Roaming\Bitcoin\
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1265 - Armory home dir : C:\Users\***\AppData\Roaming\Armory\
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1266 - Detected System Specs :
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1267 - Total Available RAM : 7.85 GB
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1268 - CPU ID string : Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1269 - Number of CPU cores : 4 cores
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1270 - System is 64-bit : True
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1271 - Preferred Encoding : cp1252
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1272 - Machine Arch : amd64
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1273 - Available HDD (ARM) : 618 GB
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1274 - Available HDD (BTC) : 618 GB
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1275 -
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1276 - Network Name: Main Network
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1277 - Satoshi Port: 8333
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1278 - Do wlt check: True
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1279 - Named options/arguments to armoryengine.py:
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - thread_count : -1
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - rescan : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - ignoreAllZC : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - rescanBalance : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - disableModules : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - port : None
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - interport : 8223
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - coverageOutputDir: None
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - forceWalletCheck: False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - regtest : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - rebuild : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - nettimeout : 2
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - datadir : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - clearMempool : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - offline : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - armoryDBDir : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - armorydb_port : 9001
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - satoshiPort : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - useTorSettings : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - netlog : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - keypool : 100
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - coverageInclude : None
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - forceOnline : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - redownload : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - rpcBindAddr : 127.0.0.1
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - armorydb_ip : 127.0.0.1
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - multisigFile : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - ram_usage : -1
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - mtdebug : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - logDisable : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - settingsPath : C:\Users\***\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - language : en
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - db_type : DB_FULL
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - doDebug : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - enableDetSign : True
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - disableConfPermis: False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - testnet : False
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - rpcport : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - satoshiHome : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - satoshiRpcport : DEFAULT
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - logFile : C:\Users\***\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1281 - verbosity : None
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1282 - Other arguments:
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1285 - ************************************************************
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:1688 - C++ block utilities loaded successfully
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:3586 - Using settings file: C:\Users\***\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:3746 - Using Language: de
2017-05-01 15:09 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-01 15:09 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.
2017-05-01 15:09 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-01 15:09 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-01 15:09 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:3586 - Using settings file: C:\Users\***\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 4
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "*** " (Encrypted)
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "*** (Watch) " (No Encryption)
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "*** " (Encrypted)
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2172 - Wallet (***): "*** " (Encrypted)
2017-05-01 15:09 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes
2017-05-01 15:09 (INFO) -- MultiSigUtils.pyc:198 - Read in Lockbox: ***
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user. Done!
2017-05-01 15:09 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-01 15:09 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-01 15:09 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-01 15:09 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-01 15:09 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:661 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\***\\AppData\\Roaming\\Bitcoin\\']
2017-05-01 15:09 (INFO) -- SDM.pyc:443 - PID of bitcoind: 4280
2017-05-01 15:09 (INFO) -- SDM.pyc:444 - PID of armory: 10708
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:661 - Executing popen: ['.\\guardian.exe', '10708', '4280']
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-01 15:09 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\***\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\***\AppData\Roaming\Armory\" --dbdir="C:\Users\***\AppData\Roaming\Armory\databases"
2017-05-01 15:09 (INFO) -- ArmoryUtils.pyc:661 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\***\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\***\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\***\\AppData\\Roaming\\Armory\\databases"']
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-01 15:09 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-01 15:09 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:09 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:09 (INFO) -- ArmoryQt.py:702 - MinimizeOnOpen is True
2017-05-01 15:09 (INFO) -- ArmoryQt.py:4561 - Dashboard switched to auto-InitSync
2017-05-01 15:09 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:09 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:09 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-01 15:10 (WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
2017-05-01 15:13 (ERROR) -- qtdialogs.pyc:5830 - Error showing TxIn
Traceback (most recent call last):
File "qtdialogs.pyc", line 5828, in showTxInDialog
File "qtdialogs.pyc", line 6001, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-01 15:13 (ERROR) -- qtdialogs.pyc:5830 - Error showing TxIn
Traceback (most recent call last):
File "qtdialogs.pyc", line 5828, in showTxInDialog
File "qtdialogs.pyc", line 6001, in __init__
TypeError: sequence item 0: expected string, QString found
2017-05-01 15:13 (ERROR) -- Traceback (most recent call last):
File "ui\MultiSigDialogs.pyc", line 1761, in doFundIt
File "qtdialogs.pyc", line 4568, in __init__
File "ui\TxFrames.pyc", line 148, in __init__
File "ui\WalletFrames.pyc", line 131, in __init__
KeyError: 0

2017-05-01 15:21 (ERROR) -- Traceback (most recent call last):
File "ui\MultiSigDialogs.pyc", line 1761, in doFundIt
File "qtdialogs.pyc", line 4568, in __init__
File "ui\TxFrames.pyc", line 148, in __init__
File "ui\WalletFrames.pyc", line 131, in __init__
KeyError: 0

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Mr.Vice on May 01, 2017, 06:47:29 AM

There is a translation in the desciption of the wallet security settings missing. Where it says "Encryped" it should be in German "Verschlüsselt". :-)

Not everything has been translated yet, and some translations seem to be broken (particularly with the Secureprint strings because of unicode). If there are no translations for a string, it will just default to the English strings.

Mr.Vice

member

Activity: 96

Merit: 10

There is a translation in the desciption of the wallet security settings missing. Where it says "Encryped" it should be in German "Verschlüsselt". :-)

tmib

newbie

Activity: 12

Merit: 0

looking forward to the 0.96 final release! thanks for the good work!

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

make install installs to $(DESTDIR)$(PREFIX):

https://github.com/goatpig/BitcoinArmory/blob/testing/Makefile.am#L39

For info, $(DESTDIR) is empty, only $(PREFIX) has anything in it, which defaults to /usr/local

You could either set a DESTDIR or use a custom PREFIX during ./configure and build yourself.

If you insist on having a built package that fits your setup, I would consider doing that for the gcc4.7 build, but you'd have to research how to force the different install path with dh-make (which calls ./configure each run). This is the script used to package .deb:

https://github.com/goatpig/BitcoinArmory/blob/testing/dpkgfiles/make_deb_package.py

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: goatpig on April 23, 2017, 01:52:43 AM

Quote

@goatpig, did you change the location of the Armory installation for 0.96? I've tried the 0.95.99.3 .deb package, but I'm getting an absence of installation at /usr/lib/ (even the directory /usr/lib/armory isn't created, /usr/local/armory & /usr/local/armorydb are created). Installation is suspiciously quick also, is there some error in the install package?

Plenty changed, courtesy of autotools. All binaries now go to /usr/local/bin, libs and python code files go to /usr/local/lib/armory. Desktop files still go to /usr/share/applications. The .deb does not distribute CPP code files anymore.

Okay, with Qubes OS, this is an issue.

/home and /usr/local are the only directories that the VM templates do not refresh in the user VMs that do the actual client work (the templates have strict firewall rules that prevent any network access except a local software update proxy VM).

This means that user VMs derived from their template VMs do not pick up any changes to the filesystem made to the /home and /usr/local directories and below. That means re-creating the user VMs every time a new Armory package is installed (I've tested this out). If the bitcoin blockchain or armory databases are installed on the actual VM disk, which is the most convenient (and also the default) option, then they must be copied off the old VM and onto the new. It's serious rigamarole, in short.

What can be done here? Basically, anywhere but /usr/local will eliminate this problem for Qubes users.

SimonBelmond

full member

Activity: 226

Merit: 100

Actually it's this one, just checked:

http://www.computershopper.com/desktops/reviews/hp-compaq-8000f-elite-ultra-slim-desktop-pc

SimonBelmond

full member

Activity: 226

Merit: 100

I think it is this one, will have to double check.

Prozessor
Typ   Intel Core i5
Modell   i5-2400s
Grundtaktfrequenz   2.5 GHz
Sockel total/frei   1 / 1

Pretty sure it's this PC:

https://support.hp.com/us-en/product/hp-compaq-8200-elite-ultra-slim-pc/5037958/manuals

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

ugh this is supposed to work... I'll try one more thing to get the deb going. What's your CPU on that machine btw?

SimonBelmond

full member

Activity: 226

Merit: 100

armory_0.95.99.3-testing-gcc4.7_amd64

Code:

armory --offline
(ERROR) ArmoryUtils.py:1232 - Error getting system details:
Traceback (most recent call last):
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1230, in
SystemSpecs = GetSystemDetails()
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1225, in GetSystemDetails
out.HddAvailB = getHddSize(BTC_HOME_DIR) / (1024**3)
File "/usr/local/lib/armory/armoryengine/ArmoryUtils.py", line 1222, in getHddSize
s = os.statvfs(adir)
OSError: [Errno 2] No such file or directory: '/home/node/.bitcoin/'
(ERROR) ArmoryUtils.py:1233 - Skipping.
(ERROR) ArmoryUtils.py:3743 - Unsupported language specified. Defaulting to English (en)
/usr/local/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
Illegal instruction (core dumped)

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Try the .deb

SimonBelmond

full member

Activity: 226

Merit: 100

Quote from: goatpig on April 23, 2017, 04:54:22 PM

Can you try the .3 gcc4.7 deb on a Ubuntu machine?

So you mean test the .deb? Or build from source?

I will have to flatten and set up my old offline PC and install Ubuntu to make it my online machine again. I will try this in the next few days. I will then use this low ram option to build the DB.

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Can you try the .3 gcc4.7 deb on a Ubuntu machine?

SimonBelmond

full member

Activity: 226

Merit: 100

Quote from: goatpig on April 23, 2017, 03:39:57 PM

Quote from: SimonBelmond on April 23, 2017, 07:28:04 AM

Wonderful, that worked now. Thank you so much! Kiss

What worked? The .deb, the txsigcollect, or both?

Installed testing version 3 over the top of testing version 2 on the win 7 x64 online machine. Now it creates unsigned tx which can be recognized by the offline testing version 2 on the Ubuntu x64. Sent a transaction went all good.

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Quote from: SimonBelmond on April 23, 2017, 07:28:04 AM

Wonderful, that worked now. Thank you so much! Kiss

What worked? The .deb, the txsigcollect, or both?

SimonBelmond

full member

Activity: 226

Merit: 100

Wonderful, that worked now. Thank you so much! Kiss

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Quote

Just checked again. Testing build 2 on both systems. Can you ELI5 gcc4.7? Where should I install this? On both systems or on my online system only?

I'm not telling you to install an older GCC, I'm telling you to try the 0.95.99.3 gcc4.7 testing build.

Quote

What about the terminal output I posted above? It seems to not be able to recognize certain parts of the TX as it states it's no legal ASCI or so.

Fixed on 0.95.99.3. You need it on your online machine to create proper txsigcollect packets.

SimonBelmond

full member

Activity: 226

Merit: 100

Quote from: goatpig on April 23, 2017, 06:16:28 AM

3rd testing build has the fix for the txsigcollet issue. I was assuming you were using that.

You can get the gcc4.7 build in the usual place:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.95.99.3-testing

Just checked again. Testing build 2 on both systems. Can you ELI5 gcc4.7? Where should I install this? On both systems or on my online system only?

What about the terminal output I posted above? It seems to not be able to recognize certain parts of the TX as it states it's no legal ASCI or so.

Topic: Armory 0.96 third testing builds (Read 4662 times)