|
Does it use a SSD or a HDD?
|
|
|
|
|
I don't put out 32 bit builds for bugfix releases unless necessary. You can expect 32bit for major releases though, but that's Linux only. If you're impatient you can create a 32bit VM for your target OS and build the binaries from there. It's not as scary as it sounds.
|
|
|
|
|
Did it die after that last line? How much RAM do you have on that machine?
|
|
|
|
Is it possible to send coins to a bech32 address with 0.96.1 + Core 0.14? If not, is it possible with any other combination of Armory and Core and which one?
Thank you!
You cannot get bech32 addresses from Armory atm. This will be part of 0.97, the next major release. The code is in dev right now, but there it hasn't been plugged in the GUI yet, and dev is unstable anyways. |
|
|
|
|
Create a file name armorydb.conf in your Armory datadir, put the argument in there.
|
|
|
|
|
Please tell me you're attempting this nonsense on an offline machine.
|
|
|
|
That's just Qt4 benign spam. how do i fix it? You learn some Python. It's benign, ignore it. Put another, what you presented is not related to what you experienced. Either figure it out yourself or present logs. |
|
|
|
Thx,
I deleted "Roaming/Armory/databases" and edited the shortcut to be this:
Shortcut->Target: "C:\Program Files (x86)\Armory\ArmoryQt.exe" --db-type=DB_BARE
No difference, armory starts, checks wallets consistency and does nothing more, no activity in process manager.
That's a DB argument, not a GUI argument. Feed it to the DB. Use the config files. |
|
|
|
Using Bisq's option "Open your external wallet for funding" gives first an error (Invalid spend value) and if clicked a second time crashes Armory. Not sure if it is Bisq's fault only but Armory shouldn't crash. -INFO - @: (SocketObject.cpp:355) POLLIN recv return 0
(ERROR) Traceback (most recent call last):
File "/usr/bin/../lib/armory/ArmoryQt.py", line 1759, in triggerProcessMutexNotification
self.uriLinkClicked(uriLink)
File "/usr/bin/../lib/armory/ArmoryQt.py", line 2055, in uriLinkClicked
return self.uriSendBitcoins(uriDict)
File "/usr/bin/../lib/armory/ArmoryQt.py", line 3518, in uriSendBitcoins
dlg.frame.prefillFromURI(uriDict)
File "/usr/lib/armory/ui/TxFrames.py", line 1463, in prefillFromURI
self.addOneRecipient(addr160, amount, message, label)
File "/usr/lib/armory/ui/TxFrames.py", line 336, in addOneRecipient
self.resolveCoinSelection()
File "/usr/lib/armory/ui/TxFrames.py", line 537, in resolveCoinSelection
raise e
RuntimeError: Invalid spend value
Traceback (most recent call last):
File "/usr/bin/../lib/armory/ArmoryQt.py", line 1759, in triggerProcessMutexNotification
self.uriLinkClicked(uriLink)
File "/usr/bin/../lib/armory/ArmoryQt.py", line 2055, in uriLinkClicked
return self.uriSendBitcoins(uriDict)
File "/usr/bin/../lib/armory/ArmoryQt.py", line 3518, in uriSendBitcoins
dlg.frame.prefillFromURI(uriDict)
File "/usr/lib/armory/ui/TxFrames.py", line 1463, in prefillFromURI
self.addOneRecipient(addr160, amount, message, label)
File "/usr/lib/armory/ui/TxFrames.py", line 336, in addOneRecipient
self.resolveCoinSelection()
File "/usr/lib/armory/ui/TxFrames.py", line 537, in resolveCoinSelection
raise e
RuntimeError: Invalid spend value
terminate called without an active exception
Aborted
Will look into it. For now, open a Send dialog and set the bitcoin: url link manually. |
|
|
|
That's just Qt4 benign spam. |
|
|
|
|
Delete your db folder and run the DB with --db-type=DB_BARE
|
|
|
|
|
Did the db crash after this? Hang? Ignored the Node entirely? Client crashed maybe?
|
|
|
|
HDD and SSD, I cannot know exactly because I use lvm, so it can reside anywhere...
Most likely the issue is that the node write operation committing the new file to disk (which happens once or twice a day) is not flushed by the time Armory goes looking for it, courtesy of cached disks (which is after processing the new block notification over P2P from the node). Looking at the code, it doesn't seem that throw is crawling all the way back to the main execution thread, so it's unexpected that it would kill the entire process. On the other hand, that also means it could be caught and handled. If you can build from source and are willing to tinker with that stuff, I can tell you what code to add to try and fix this. |
|
|
|
It seems it does:
Compare the file creation timestamp to the log message error timestamp. What kind of hardware does your blockchain data reside on? How long do you let the DB run? |
|
|
|
|
What OS you on? Also, at the moment it happens, does the missing blk file reside on disk? Is restarting the DB fixing it?
|
|
|
|
To be able to select SegWit addresses on the offline machine, you have to run the proper cli args. Look at the changelog for that: https://github.com/goatpig/BitcoinArmory/blob/testing/changelog.txt#L14The change selector will not pick a nested SW return address if there isn't at least one SW input in the tx. This is because SW was deployed as soft fork, therefor an opt-in feature. The implementation of SW in Armory intents to respect that disposition. Think of it this way: the software will not lead to coins in opt-in/new script types without some guarantee that there was deliberate user intent. |
|
|
|
Sorting is a PITA to implement in GUI so don't hold your breath for that one.
how about search? I have plans for some advanced search/sorting but not in a 0.96 iteration. |
|
|
|
|
I haven't looked at this one in a while, that's probably the issue.
|
|
|
|
|
Show Posts
