Has anyone here successfully run 0.90.99.4 on any OSX version? I downloaded and ran it on 10.9, but that system also already has a build environment on it.
It looks like the build has the QNetwork.so error on 10.9.2 and 10.9.1. I have successfully run it on a 10.8 VM and 10.9 host. But both have the build environments...
Topic: Please Help Test Armory 0.91-beta! - page 7. (Read 21332 times)
- No more choking on bad blocks written by Bitcoin-Qt/bitcoind
Because I believe that the data is dumped to the blk*.dat files after bitcoin-qt/bitcoind has processed and indexed it. If it fails to write out the full block and then continues writing, it won't ever notice unless it has to explicitly fetch that block for some reason. I suspect that would only be relevant if that particular block had a tx relevant to your wallet (probably core wallet.dat). As such, errors are effectively ignored until you try to re-index.
In our case, we're rescanning those blk*.dat files pretty frequently, and were under the assumption that there was some consistency in there. Apparently not. And it was causing Armory seg faults.
- No more choking on bad blocks written by Bitcoin-Qt/bitcoind
forgot the double dash.. that's working now, but it's now i have another issue.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file.
if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error
I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file.
Code:
2014-03-26 15:25 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file
2014-03-26 15:25 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf
2014-03-26 15:25 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf
2014-03-26 15:25 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', u'G:\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'DC:F']
2014-03-26 15:25 (INFO) -- SDM.pyc:486 - icacls returned:
2014-03-26 15:25 (ERROR) -- ArmoryQt.py:1966 - Failed to setup SDM
Traceback (most recent call last):
File "ArmoryQt.py", line 1961, in startBitcoindIfNecessary
File "SDM.pyc", line 329, in setupSDM
File "SDM.pyc", line 492, in readBitcoinConf
IOError: [Errno 13] Permission denied: u'G:\\Bitcoin\\bitcoin.conf'
if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error
Code:
2014-03-26 15:26 (ERROR) -- BDM.pyc:1383 - Error processing BDM input
2014-03-26 15:26 (ERROR) -- BDM.pyc:1385 - Received inputTuple: Passthrough [15, 50260050, True, 'enableZeroConf', u'G:\\Armory\\mempool.bin']
2014-03-26 15:26 (ERROR) -- BDM.pyc:1386 - Error processing ID (50260050)
2014-03-26 15:26 (ERROR) -- BDM.pyc:1387 - ERROR:
Traceback (most recent call last):
File "armoryengine\BDM.pyc", line 1343, in run
File "CppBlockUtils.pyc", line 1883, in enableZeroConf
NotImplementedError: Wrong number or type of arguments for overloaded function 'BlockDataManager_LevelDB_enableZeroConf'.
Possible C/C++ prototypes are:
BlockDataManager_LevelDB::enableZeroConf(string,bool)
BlockDataManager_LevelDB::enableZeroConf(string)
I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced.
bitcoin.conf: did you run Armory as admin? Armory typically sets the permission of the bitcoin.conf to readonly for the current user (since it contains a username and password). And if Armory can't read it, I bet bitcoin core can't read it either, which maybe explains the other error. Though, it's strange error, that looks like what happens when you upgrade the repo without rebuilding the C++ code (enableZeroConf prototype did change recently, so if you only updated the python but didn't recompile, you'd see this error). But I see you're in windows so I don't expect that to be the problem...
Armory and Bitcoin is ran as a user. I end up having to create a new bitcoin.conf file each time I get this permission error. I am using the windows build from the first post.
forgot the double dash.. that's working now, but it's now i have another issue.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file.
if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error
I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file.
Code:
2014-03-26 15:25 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file
2014-03-26 15:25 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf
2014-03-26 15:25 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf
2014-03-26 15:25 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', u'G:\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'DC:F']
2014-03-26 15:25 (INFO) -- SDM.pyc:486 - icacls returned:
2014-03-26 15:25 (ERROR) -- ArmoryQt.py:1966 - Failed to setup SDM
Traceback (most recent call last):
File "ArmoryQt.py", line 1961, in startBitcoindIfNecessary
File "SDM.pyc", line 329, in setupSDM
File "SDM.pyc", line 492, in readBitcoinConf
IOError: [Errno 13] Permission denied: u'G:\\Bitcoin\\bitcoin.conf'
if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error
Code:
2014-03-26 15:26 (ERROR) -- BDM.pyc:1383 - Error processing BDM input
2014-03-26 15:26 (ERROR) -- BDM.pyc:1385 - Received inputTuple: Passthrough [15, 50260050, True, 'enableZeroConf', u'G:\\Armory\\mempool.bin']
2014-03-26 15:26 (ERROR) -- BDM.pyc:1386 - Error processing ID (50260050)
2014-03-26 15:26 (ERROR) -- BDM.pyc:1387 - ERROR:
Traceback (most recent call last):
File "armoryengine\BDM.pyc", line 1343, in run
File "CppBlockUtils.pyc", line 1883, in enableZeroConf
NotImplementedError: Wrong number or type of arguments for overloaded function 'BlockDataManager_LevelDB_enableZeroConf'.
Possible C/C++ prototypes are:
BlockDataManager_LevelDB::enableZeroConf(string,bool)
BlockDataManager_LevelDB::enableZeroConf(string)
I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced.
bitcoin.conf: did you run Armory as admin? Armory typically sets the permission of the bitcoin.conf to readonly for the current user (since it contains a username and password). And if Armory can't read it, I bet bitcoin core can't read it either, which maybe explains the other error. Though, it's strange error, that looks like what happens when you upgrade the repo without rebuilding the C++ code (enableZeroConf prototype did change recently, so if you only updated the python but didn't recompile, you'd see this error). But I see you're in windows so I don't expect that to be the problem...
forgot the double dash.. that's working now, but it's now i have another issue.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file.
if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error
I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced.
when i let armory control bitcoin, it corrupts the bitcoin.conf file somehow. i am unable to open the file.
Code:
2014-03-26 15:25 (INFO) -- SDM.pyc:461 - Reading bitcoin.conf file
2014-03-26 15:25 (INFO) -- SDM.pyc:480 - Setting permissions on bitcoin.conf
2014-03-26 15:25 (INFO) -- SDM.pyc:483 - Setting permissions on bitcoin.conf
2014-03-26 15:25 (INFO) -- ArmoryUtils.pyc:515 - Executing popen: ['icacls', u'G:\\Bitcoin\\bitcoin.conf', '/inheritance:r', '/grant:r', 'DC:F']
2014-03-26 15:25 (INFO) -- SDM.pyc:486 - icacls returned:
2014-03-26 15:25 (ERROR) -- ArmoryQt.py:1966 - Failed to setup SDM
Traceback (most recent call last):
File "ArmoryQt.py", line 1961, in startBitcoindIfNecessary
File "SDM.pyc", line 329, in setupSDM
File "SDM.pyc", line 492, in readBitcoinConf
IOError: [Errno 13] Permission denied: u'G:\\Bitcoin\\bitcoin.conf'
if i don't let armory control bitcoin, the bottom right says "connected (0 blocks)" and get this error
Code:
2014-03-26 15:26 (ERROR) -- BDM.pyc:1383 - Error processing BDM input
2014-03-26 15:26 (ERROR) -- BDM.pyc:1385 - Received inputTuple: Passthrough [15, 50260050, True, 'enableZeroConf', u'G:\\Armory\\mempool.bin']
2014-03-26 15:26 (ERROR) -- BDM.pyc:1386 - Error processing ID (50260050)
2014-03-26 15:26 (ERROR) -- BDM.pyc:1387 - ERROR:
Traceback (most recent call last):
File "armoryengine\BDM.pyc", line 1343, in run
File "CppBlockUtils.pyc", line 1883, in enableZeroConf
NotImplementedError: Wrong number or type of arguments for overloaded function 'BlockDataManager_LevelDB_enableZeroConf'.
Possible C/C++ prototypes are:
BlockDataManager_LevelDB::enableZeroConf(string,bool)
BlockDataManager_LevelDB::enableZeroConf(string)
I've tried to rescan, rescan/rebuild as well as factory reset. I'm on Win7 and BitcoinQT 0.9 fully synced.
is the datadir flag still working? i'm on win7 and armory is ignoring the datadir location and using the default location.
I just noticed yesterday that --datadir fails if the target directory doesn't exist yet. Rather than bailing, it just switches to using the default directory. We're still not sure exactly how we want to deal with that yet.
Besides that, I've been using --datadir constantly, and it works fine (for me)
is the datadir flag still working? i'm on win7 and armory is ignoring the datadir location and using the default location.
No wonder it wouldn't work, the WinXP specific code was not in this branch. Fixed now, you'll have to wait for the next build.
OK, thanks. I'm having all sorts of issues trying to move coins from a hot wallet to my cold storage since moving to this release + 0.9.0 BitcoinQT.
This appears to only impact when i do a one to many transaction i.e. Sending from one source address to multiple output addresses.
Anyone else encountering the same issue?
Also which log file should i be checking for.
This appears to only impact when i do a one to many transaction i.e. Sending from one source address to multiple output addresses.
Anyone else encountering the same issue?
Also which log file should i be checking for.
Just use Help->Submit Bug Report :-)
I'm having all sorts of issues trying to move coins from a hot wallet to my cold storage since moving to this release + 0.9.0 BitcoinQT.
This appears to only impact when i do a one to many transaction i.e. Sending from one source address to multiple output addresses.
Anyone else encountering the same issue?
Also which log file should i be checking for.
This appears to only impact when i do a one to many transaction i.e. Sending from one source address to multiple output addresses.
Anyone else encountering the same issue?
Also which log file should i be checking for.
I dont think I like the "secure updater" thing. It sounds dangerous.
Also, you defenetly should implement Multisig to armory (a nice gui that would allow a user to generate a multisig address)
I would try this version but I have bitcoins that I dont want to risk so I'll wait for a stable release
Also, you defenetly should implement Multisig to armory (a nice gui that would allow a user to generate a multisig address)
I would try this version but I have bitcoins that I dont want to risk so I'll wait for a stable release
Not sure why it sounds "dangerous". It's exactly the opposite. It lets you download the latest version and verifies all the digital signatures for you, so you don't have to install and figure out how to use GPG, and then find our GPG key and verify fingerprints. (granted, you should do that the first time you get Armory, but after that assuming you got a good copy, you will always be able to get the next version with the same security but without any effort). We are not implementing automatic updates yet. We're simply providing a mechanism for downloading signed installers and checking the signatures for you.
Multisig is my top priority after this version is out. Coming soon!
I dont think I like the "secure updater" thing. It sounds dangerous.
Also, you defenetly should implement Multisig to armory (a nice gui that would allow a user to generate a multisig address)
I would try this version but I have bitcoins that I dont want to risk so I'll wait for a stable release
Also, you defenetly should implement Multisig to armory (a nice gui that would allow a user to generate a multisig address)
I would try this version but I have bitcoins that I dont want to risk so I'll wait for a stable release
Am I glad I backed up my wallets, I launched it to the majority of my comments being wiped out:-
The comment issue is now fixed in branch 0.91-dev
EDIT: just to be clear, the comments were never deleted from your wallet, they were not displayed, as an unattended consequence of the 99% crash fix.
So far, everyone who has reported this "image not found" error on OSX is running 10.9.2. I think. Please tell me if you see this error and are not running 10.9.2.
The error is not a missing file, because the exact same package seems to work on other versions of OSX. It's that the same dynamic object used by earlier OSX versions doesn't seem to be compatible with 10.9.2. It's possible we just might need to build a 10.9.2-specific version. Ugh!
Go figure I bet it's finally working on 10.9.1 and then Apple goes ahead and makes yet another incompatible version!
The error is not a missing file, because the exact same package seems to work on other versions of OSX. It's that the same dynamic object used by earlier OSX versions doesn't seem to be compatible with 10.9.2. It's possible we just might need to build a 10.9.2-specific version. Ugh!
Go figure I bet it's finally working on 10.9.1 and then Apple goes ahead and makes yet another incompatible version!
I am running OSX Mavericks and when I try to run the app (clicking in applications folder) literally nothing happens? 
Where should I go from here?
Trying to open via Armory located within MacOS folder gives me
Where should I go from here?
Trying to open via Armory located within MacOS folder gives me
Code:
xxxx's-iMac:MacOS xxxx$ /Applications/Armory.app/Contents/MacOS/Armory
(ERROR) Traceback (most recent call last):
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 37, in
from ui.toolsDialogs import MessageSigningVerificationDialog
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/toolsDialogs.py", line 15, in
from qtdialogs import MIN_PASSWD_WIDTH, DlgPasswd3, createAddrBookButton,\
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 25, in
from ui.UpgradeDownloader import UpgradeDownloaderDialog
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/UpgradeDownloader.py", line 3, in
from PyQt4.QtNetwork import *
ImportError: dlopen(/Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtNetwork.so, 2): Library not loaded: /Users/joeschmoe/BitcoinArmory/osxbuild/workspace/install/qt/lib/QtNetwork.framework/Versions/4/QtNetwork
Referenced from: /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtNetwork.so
Reason: image not found
Traceback (most recent call last):
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 37, in
from ui.toolsDialogs import MessageSigningVerificationDialog
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/toolsDialogs.py", line 15, in
from qtdialogs import MIN_PASSWD_WIDTH, DlgPasswd3, createAddrBookButton,\
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 25, in
from ui.UpgradeDownloader import UpgradeDownloaderDialog
File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/UpgradeDownloader.py", line 3, in
from PyQt4.QtNetwork import *
ImportError: dlopen(/Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtNetwork.so, 2): Library not loaded: /Users/joeschmoe/BitcoinArmory/osxbuild/workspace/install/qt/lib/QtNetwork.framework/Versions/4/QtNetwork
Referenced from: /Applications/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtNetwork.so
Reason: image not found
I'm getting this:
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Code:
Traceback (most recent call last):
File "armoryqt.py", line 38, in
from PyQt4.QtCore import *
ImportError: No module named PyQt4.QtCore
The previous version worked fine so not sure what that's about. Don't really know how to fix it either...
Anything I can try here?
Ok then. I've gone back to the previous version which is working fine.
Also, is it correct it's on a system with 512 MB of RAM?
Yes.Quote
Are you trying to run this online?
No. As I said in my first post, this is intended to be an offline wallet, using a cheap netbook running XP.I tried using Process Monitor. That suggests Armory:
- Successfully finds _CppBlockUtils.pyd
- Fails to find registry key HKCU\Control Panel\Desktop\MultiUILanguageId
- Fails to find _CppBlockUtils.pyd.2.Manifest
- Closes CppBlockUtils.pyd
- Fails to find ArmoryQt.pyc
- Fails to find ALL.pyc
- Fails to find ArmoryUtils.pyc
- Fails to find CppBlockUtils.pyc
- Closes various files and registry keys and exits.
No wonder it wouldn't work, the WinXP specific code was not in this branch. Fixed now, you'll have to wait for the next build.
If you don't use P2SH anywhere, it works fine.
If you use P2SH, it will likely "work", but the offline computer will show useless info for any P2SH addresses. I don't recommend using it, since part of the security comes from being able to review the entirety of the tx on the offline computer.
If you use P2SH, it will likely "work", but the offline computer will show useless info for any P2SH addresses. I don't recommend using it, since part of the security comes from being able to review the entirety of the tx on the offline computer.
Does this version (as network connected) still work with old version (as cold storage)?
I guess the old version can't sign P2SH?
I guess the old version can't sign P2SH?
Jump to: