|
You want to build the current state of testing, has a fix for this.
|
|
|
|
|
The only changes "in testing" are DB related, the wallet stuff has no issue.
|
|
|
|
Without logs no one could help you.
|
|
|
|
|
Fix is in the repo, no builds for it yet.
|
|
|
|
|
You have to type 'armory' without caps.
|
|
|
|
@goatpig, Hi, , just upgraded my off-line Armory from 0.93.3 to 0.96.03-testing version/ Everything vent smoothly but when I did Tools==> MessageSigning/Verification==> click select from Address Book to choose address for signing message the error window appears with the message " ArmoryQT.exe has stopped working "/ Repeated this a few times with the same result. The log is pasterbined https://pastebin.com/raw/juPni66GCan't reproduce this either. Can you detail the steps you take? Step-by-step: Tools==> click Message Signing/... ==> mouse pointer on Book icon ( right near sign with Address:) and click on it ==> error window Nvm, figured it out. Wasn't running in offline mode. |
|
|
|
@goatpig, Hi, , just upgraded my off-line Armory from 0.93.3 to 0.96.03-testing version/ Everything vent smoothly but when I did Tools==> MessageSigning/Verification==> click select from Address Book to choose address for signing message the error window appears with the message " ArmoryQT.exe has stopped working "/ Repeated this a few times with the same result. The log is pasterbined https://pastebin.com/raw/juPni66GCan't reproduce this either. Can you detail the steps you take? |
|
|
|
Thanks for the report, will look into it.
Help -> About doesn't work either. Didn't check all menu entries. arg(self, QString, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
Can't reproduce. Is this 0.96 or the testing branch? Can you show me the line # as well? |
|
|
|
|
Just show me the output of ./configure, don't need config.log, it's confusing searching that huge file for errors.
|
|
|
|
After another go at it, it worked. Almost.. Can you help me understand why many of my Labels are missing? These are stored in the .wallet file is that right? I've even had this issue also when moving from one Armory 0.93.3 to another 0.93.3.
You mean they missing in the main tx ledger? That's a known issue, fixed in the testing builds. Only one of my the wallets has an extra copy named with "_encrypt", even though I have more than one wallet encrypted, and so why would it keep around the same named wallet WITHOUT the "_encrypt" suffix?
Armory will never delete redundant wallet files, even though it won't load them. Some times ago you performed some operations on your wallets resulted in creating an encrypted copy, and this is what you are seeing now. PS -- I PM'd you only for sending you the log file links, to minimize the exposure of my personal information like wallet id's and names, computer hardware, OS, etc. I'm sure you can respect that.
Then post here and PM me just the logs. I need to see the convo and my previous replies to remember the context. It's painfully hard to make sense of what's going on if you break the thread into pieces. Consider that I can end up juggling as many as a dozen cases simultaneously. |
|
|
|
|
Thanks for the report, will look into it.
|
|
|
|
|
Start ArmoryDB manually from the terminal/command prompt, then run armoryqt.
|
|
|
|
-INFO - 08:24:05.281: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 08:24:05.578: (..\DatabaseBuilder.cpp:268) parsed block file #0
-DEBUG - 08:24:05.578: (..\Blockchain.cpp:242) Organizing chain
Your block data folder has very little data in it, basically nothing. The settings file is not a log. |
|
|
|
Phenom X4 9150e, from 2008. I believe it supports SSE4a, but I don't know yet what maes is.
SSE4a is not full SSE4, and the build you are trying to run is using maes and mcplmul as well, and your CPU is lacking the registers for that. This one?
No you want to follow the instruction from your previous thread: https://bitcointalk.org/index.php?topic=1983988.msg19773410#msg19773410Armory for Linux is target at Ubuntu 16.04 so you shouldn't have as many issues getting it to build this time. Make sure you install swig as well, as the configure script does not check for it (will fix that eventually): sudo apt-get install swig
|
|
|
|
|
How old is your CPU? It probably does not support -maes nor sse4. You gonna have to build from source to get that working.
|
|
|
|
|
Show Posts
