Topic: Armory - Discussion Thread - page 40. (Read 521749 times)
Hi I'm running Xubuntu 14.04LTS (64) and trying to set Armoury up. When I installed bitcoin-qt from the PPA it asked me to specify a place to store it. So I chose my Documents folder as my /home folder is on a 1TB SSHD while my / folder is on a small SSD. I've pointed Armoury to /documents but it still can't see it. Also I would like to be able to safely move all the bitcoin-qt folders and files to its own directory inside /documents instead of them all being spread out in the folder.
Sweet
Any way to destroy dust in armory? I don't see a way to manually give dust b gone private keys to clean
.
.
.
I cant, the dust is .000000001
https://blockchain.info/tx/3e5b3a033840a9ff4a9c24b1980c07e0823a171e4001ef03953fed0da1aa9da0
.
.
.
I cant, the dust is .000000001
https://blockchain.info/tx/3e5b3a033840a9ff4a9c24b1980c07e0823a171e4001ef03953fed0da1aa9da0
Not yet, but this sounds like a great application for Armory's new plugin system.
I'll put something together and post it to try out with the latest testing version. It will be testnet only unless you build your own Armory from source.
Any way to destroy dust in armory? I don't see a way to manually give dust b gone private keys to clean
Some bastards found a way to confirm some
So you just toss away everything after x.xx ?Some bastards found a way to confirm some
Hell, send it to me lol
I cant, the dust is .000000001
https://blockchain.info/tx/3e5b3a033840a9ff4a9c24b1980c07e0823a171e4001ef03953fed0da1aa9da0
Any way to destroy dust in armory? I don't see a way to manually give dust b gone private keys to clean
Some bastards found a way to confirm some
So you just toss away everything after x.xx ?Some bastards found a way to confirm some
Hell, send it to me lol
Any way to destroy dust in armory? I don't see a way to manually give dust b gone private keys to clean
Some bastards found a way to confirm some
Some bastards found a way to confirm some
When setting this up or the first time with a new bitcoin installation as well. Should I install the windows client first, download the blockchain which would be about 24hrs if not less, then install armory or install both at the same time then DL the chain etc. ?
After installing both, you can just run Armory, and it will start Bitcoin for you. Both applications will build whatever is missing even if that is everything.
When setting this up or the first time with a new bitcoin installation as well. Should I install the windows client first, download the blockchain which would be about 24hrs if not less, then install armory or install both at the same time then DL the chain etc. ?
Edit:
Edit:
Quote
Update: If you already have a verified copy of Armory version 0.91 or higher, you can use the new secure downloader feature to get upgrades and/or installers for other systems. See the next section for more info. If you don't have a verified copy of Armory yet, you should follow these instructions to verify the first Armory installer you download via GPG.
Armory is used by some of the most heavily-invested, and most paranoid Bitcoin enthusiasts for maximum privacy and security. If you are in this category, it is recommended you verify that your Armory installers have not been altered in any way. Armory Ubuntu/Debian packages (*.deb files) are signed directly using our Offline Signing Key (GPG) (0x98832223). And each release comes with a signed file containing the SHA256 hashes of each installer. Unfortunately, it is not easy to verify these signatures unless you have access to a Linux machine. At the moment, the verification procedure on Windows is very difficult.
Even if it is very difficult, would be nice to know how unless in my haste you said how to and I just glazed over it. Or is verification a thing that's technically needed in online systems only or just all around better to do it for online and offline systems. Armory is used by some of the most heavily-invested, and most paranoid Bitcoin enthusiasts for maximum privacy and security. If you are in this category, it is recommended you verify that your Armory installers have not been altered in any way. Armory Ubuntu/Debian packages (*.deb files) are signed directly using our Offline Signing Key (GPG) (0x98832223). And each release comes with a signed file containing the SHA256 hashes of each installer. Unfortunately, it is not easy to verify these signatures unless you have access to a Linux machine. At the moment, the verification procedure on Windows is very difficult.
Well, as promised, I did track down the issue. 
Let's just say this was another one of those weird, WTF gotchas that seem to happen only in OS X. None of the proposed solutions I found online worked exactly. When I finally tried a modified version of a solution, it worked, and yet I was left scratching my head, wondering why it worked but what was in the build script didn't work.
Anyway, a full rebuild isn't required to take advantage of the fix, although I'd definitely recommend a full rebuild whenever possible. It's the safest way to incorporate the changes I've made for 0.92.
Let's just say this was another one of those weird, WTF gotchas that seem to happen only in OS X. None of the proposed solutions I found online worked exactly. When I finally tried a modified version of a solution, it worked, and yet I was left scratching my head, wondering why it worked but what was in the build script didn't work.Anyway, a full rebuild isn't required to take advantage of the fix, although I'd definitely recommend a full rebuild whenever possible. It's the safest way to incorporate the changes I've made for 0.92.
any chance you can post the version you've fixed... so we can re-test it and see if the crash and hang bugs disappeared when you fixed the Python name problem?
https://github.com/etotheipi/BitcoinArmory/tree/devel has the latest commits for now. You can find the fix over there. Just be aware, once again, that we're still working out kinks here and there. (I was also gone over the weekend.)
Also, I believe you were asking about testing on Yosemite? I installed Yosemite DP2 on a VM and gave Armory a quick spin a few days ago. The Armory GUI fired up without issue, and I was able to run the various Armory unit tests without issue. Just keep in mind that I didn't bang on the GUI particularly hard.
Re the title. just to explain a bit more detail... Im saying that the title of the App has changed from being called Armory to Python. i.e.: previous Mac builds of Armory, the application was called 'Armory' and when you had to Force Quit it, in the list of Apps it was called Armory.. and it said Armory in the window's title bar (at the top of the screen). Now the app seems to be called 'Python', and in the Force Quit window its called Python, and the Window title bar says Python, so I'm assuming something has accidentally changed the name of the App to be called Python. And if this isn't the case when you run it and you're not seeing what I'm seeing, then that may be an issue.
Note on this: because it takes a few hours to do a full redownload and rebuild of all the depedencies, I typically don't do it. However, it's entirely possible that there is residuals from the last build that are causing issues, and I should stop taking the shortcut and always do a rebuild.
Well, as promised, I did track down the issue.
Let's just say this was another one of those weird, WTF gotchas that seem to happen only in OS X. None of the proposed solutions I found online worked exactly. When I finally tried a modified version of a solution, it worked, and yet I was left scratching my head, wondering why it worked but what was in the build script didn't work.Anyway, a full rebuild isn't required to take advantage of the fix, although I'd definitely recommend a full rebuild whenever possible. It's the safest way to incorporate the changes I've made for 0.92.
Hi Doug,
any chance you can post the version you've fixed... so we can re-test it and see if the crash and hang bugs disappeared when you fixed the Python name problem?
I also have noticed some potential double-spend problems that i emailed Alan about a couple of weeks ago but not heard anything about those. i didn't want to post these in open forum for obvious reasons... but i've not had a response yet.
-- Jez
Re the title. just to explain a bit more detail... Im saying that the title of the App has changed from being called Armory to Python. i.e.: previous Mac builds of Armory, the application was called 'Armory' and when you had to Force Quit it, in the list of Apps it was called Armory.. and it said Armory in the window's title bar (at the top of the screen). Now the app seems to be called 'Python', and in the Force Quit window its called Python, and the Window title bar says Python, so I'm assuming something has accidentally changed the name of the App to be called Python. And if this isn't the case when you run it and you're not seeing what I'm seeing, then that may be an issue.
Note on this: because it takes a few hours to do a full redownload and rebuild of all the depedencies, I typically don't do it. However, it's entirely possible that there is residuals from the last build that are causing issues, and I should stop taking the shortcut and always do a rebuild.
Well, as promised, I did track down the issue.
Let's just say this was another one of those weird, WTF gotchas that seem to happen only in OS X. None of the proposed solutions I found online worked exactly. When I finally tried a modified version of a solution, it worked, and yet I was left scratching my head, wondering why it worked but what was in the build script didn't work.Anyway, a full rebuild isn't required to take advantage of the fix, although I'd definitely recommend a full rebuild whenever possible. It's the safest way to incorporate the changes I've made for 0.92.
Re the title. just to explain a bit more detail... Im saying that the title of the App has changed from being called Armory to Python. i.e.: previous Mac builds of Armory, the application was called 'Armory' and when you had to Force Quit it, in the list of Apps it was called Armory.. and it said Armory in the window's title bar (at the top of the screen). Now the app seems to be called 'Python', and in the Force Quit window its called Python, and the Window title bar says Python, so I'm assuming something has accidentally changed the name of the App to be called Python. And if this isn't the case when you run it and you're not seeing what I'm seeing, then that may be an issue.
Note on this: because it takes a few hours to do a full redownload and rebuild of all the depedencies, I typically don't do it. However, it's entirely possible that there is residuals from the last build that are causing issues, and I should stop taking the shortcut and always do a rebuild.
On a sidenote, I have a 3D printer and use Makerware for slicing and sending to the printer. I noticed during install it looks like they do the exact same thing as us: bundled python with PyQt. However, I think they use Qt5. They use virtual-env, which I don't think our OSX solution uses. It might be worth digging a bit into what they are doing, because it sounds like they've done almost the same thing, but much more robustly.
Armory is the only App (and believe me, i have plenty) that seems to have this problem running on macs. its unstable with frequent crashes and hangs... and its become worse again with the new OS Yosemite. I urge you to be running that in your QA suite so you can ensure that your app works on the latest OS and not just older ones... especially as Apple is about to do an open beta to all members of the public. It seems unlikely to be Apple breaking things with every OS change, since every other App seems to work perfectly. I think its something thats been in Mac Armory the whole time that is causing you a problem with every new build and every new OS... perhaps a legacy bug or a memory leak or something like that. its not likely that apple is the cause of these hangs and crashes, and yet every other app works fine.
You're correct, there have been issues getting the Mac build to be completely stable. Part of the problem, unfortunately, is our reliance on the Qt framework and our attempt to avoid Apple's developer tools as much as possible (e.g., Xcode). There are several poorly documented workarounds that at least some Qt-reliant programs use in order to work on OS X. Even with those fixed, there are still more issues that one will notice if they execute Armory from the command line and see what appears on the terminal. 10.9 has been out for at least a year (dev previews included) and 10.9-specific fixes are still getting committed to the Qt codebase. Even then, some of the fixes are for Qt5, with people having to ask for Qt4 backports. (We still use Qt4. For various reasons, it may be awhile before we move to Qt5. I spent a day attempting a code upgrade. The results opened a big can of worms.) I've been in touch with the Qt devs, trying to get them to take a look and see if they know why we might be seeing Qt-related crashes. I haven't had much luck so far. I also can only hope the devs don't use 10.10 as an excuse to finally kill Qt4 support. (Qt 5.3.1 does have initial 10.10 support, thankfully.)
In addition, I can only do so much testing on my hardware and in VMs. I do see the occasional Qt-related crash on my hardware which may or may not be related to what I wrote above. That's about it. I've seen reports from people who have seen more crashes, or seem to be completely unable to even get Armory to start. I can't seem to reproduce most of these issues, unfortunately. Maybe there are further workarounds I need to implement. Maybe there's a subtle bug that's crashing OS X but not Linux or Windows. Maybe it's something else, or all of the above. I'm doing the best I can to fix everything.
Quote
Re the title. just to explain a bit more detail... Im saying that the title of the App has changed from being called Armory to Python. i.e.: previous Mac builds of Armory, the application was called 'Armory' and when you had to Force Quit it, in the list of Apps it was called Armory.. and it said Armory in the window's title bar (at the top of the screen). Now the app seems to be called 'Python', and in the Force Quit window its called Python, and the Window title bar says Python, so I'm assuming something has accidentally changed the name of the App to be called Python. And if this isn't the case when you run it and you're not seeing what I'm seeing, then that may be an issue.
When you say previous builds, which ones are you talking about? We incorporated a new build process awhile back (starting with 0.9 or 0.91, I believe) that may have changed something. I do have the program title set in Info.plist, so there's something else at play. I'll look into it. A quick search shows that this is a common problem and that, once again, solutions aren't necessarily straightforward.
Quote
I can send you any log files you want.. please tell me what to send, and where to send it.
Send me a PM and we'll get this going. The logs should be useful for the crashes.
Thanks for the feedback and the help!
New version seems very unstable & broken (0.91.99.8-beta). first time i ran it, it crashed within seconds (Python error). Second time i ran it, it hung within seconds. Needed to 'Force Quit' the app as it wouldnt close, but just hung there.
Also, Window title says Python instead of Armory.
This is the Mac version.
Also, Window title says Python instead of Armory.
This is the Mac version.
Well, it is a dev build.
We're still working out various kinks. Please submit any logs you might have.Regarding the Mac build, I haven't had any problems running it ever since I checked in some fixes a few days ago that got the Mac build back on track. (It was broken for awhile.) Also, regarding the Python/Armory thing, I'm not sure offhand if there's a good way to handle that. I believe it has to do with the way that the Mac build executes Armory. I can look into it. I just can't promise anything right now.
Hi Doug
Thanks, i accept its a dev build... but i have noticed that thisisnt a new issue. armory mac compatibility is still a serious problem and has always been.
Armory is the only App (and believe me, i have plenty) that seems to have this problem running on macs. its unstable with frequent crashes and hangs... and its become worse again with the new OS Yosemite. I urge you to be running that in your QA suite so you can ensure that your app works on the latest OS and not just older ones... especially as Apple is about to do an open beta to all members of the public. It seems unlikely to be Apple breaking things with every OS change, since every other App seems to work perfectly. I think its something thats been in Mac Armory the whole time that is causing you a problem with every new build and every new OS... perhaps a legacy bug or a memory leak or something like that. its not likely that apple is the cause of these hangs and crashes, and yet every other app works fine.
Re the title. just to explain a bit more detail... Im saying that the title of the App has changed from being called Armory to Python. i.e.: previous Mac builds of Armory, the application was called 'Armory' and when you had to Force Quit it, in the list of Apps it was called Armory.. and it said Armory in the window's title bar (at the top of the screen). Now the app seems to be called 'Python', and in the Force Quit window its called Python, and the Window title bar says Python, so I'm assuming something has accidentally changed the name of the App to be called Python. And if this isn't the case when you run it and you're not seeing what I'm seeing, then that may be an issue.
I can send you any log files you want.. please tell me what to send, and where to send it.
thanks
-- Jez
New version seems very unstable & broken (0.91.99.8-beta). first time i ran it, it crashed within seconds (Python error). Second time i ran it, it hung within seconds. Needed to 'Force Quit' the app as it wouldnt close, but just hung there.
Also, Window title says Python instead of Armory.
This is the Mac version.
Also, Window title says Python instead of Armory.
This is the Mac version.
Well, it is a dev build.
We're still working out various kinks. Please submit any logs you might have.Regarding the Mac build, I haven't had any problems running it ever since I checked in some fixes a few days ago that got the Mac build back on track. (It was broken for awhile.) Also, regarding the Python/Armory thing, I'm not sure offhand if there's a good way to handle that. I believe it has to do with the way that the Mac build executes Armory. I can look into it. I just can't promise anything right now.
New version seems very unstable & broken (0.91.99.8-beta). first time i ran it, it crashed within seconds (Python error). Second time i ran it, it hung within seconds. Needed to 'Force Quit' the app as it wouldnt close, but just hung there.
Also, Window title says Python instead of Armory.
This is the Mac version.
Also, Window title says Python instead of Armory.
This is the Mac version.
Hi
I upgraded from Armory 0.90 directly to 0.91.2, all went fine ( on a win 8.1 64bit OS )
When I realized that 0.91.2 is the "Armory Testing (unstable) 0.91.2" version
I simply installed Armory 0.91.1 over 0.91.2, and it worked.
My question is, will I run into any issues because I installed an older version 0.91.1 over the newer one 0.91.2 ?
Thanks for clarification.
I upgraded from Armory 0.90 directly to 0.91.2, all went fine ( on a win 8.1 64bit OS )
When I realized that 0.91.2 is the "Armory Testing (unstable) 0.91.2" version
I simply installed Armory 0.91.1 over 0.91.2, and it worked.
My question is, will I run into any issues because I installed an older version 0.91.1 over the newer one 0.91.2 ?
Thanks for clarification.
No unless wallet has a new version and you created a new one
You should use 912 tho it's not unstable as it says
Bummer! When I updated the torrent and re-signed the installer hashes, I accidentally left the "Testing (Unstable)" on 0.91.2 which is what is shown in the secure downloader. I'll have to fix that.
On the other hand, it's listed on our website as the latest stable version. So there's that...
Looks like you also forgot to merge 0.91.2 into the Master tree on GitHub. I run Arch Linux so I used the AUR package that pulls from git and I got 0.91.1.
Hi guys,
i have a bug in Armory and this is annoying cuz im just waiting for a transaction now.
Armory Version : 0.91.2 x64
Windows 7
What i see first is Armory disconnect / Reconnect every 5 second.
I check on the web and i found some people with the same issue, but in majority of time they repair it with adding memory or get a faster hard drive.
In my case its not the problem, i have 32Go of Ram and two SSD Hard-drive in RAID 1.
When i check the log file this is an example of what is see :
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync
2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Offline"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync
2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Offline"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync
2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, Stat
So i tried a couple of thing to try to understand the bug, but this just give me more question
When i reboot my computer and just run Armory everything working fine.
But if i start Google Chrome and go On Gmail, Armory Disconnect
I do not understand but i can reproduce the bug like that.
Link: http://youtu.be/Q8Vve_VbvL8
The wallet don't disconnect only on Gmail, this is just an example. When i have a lot of program open the wallet bug to.
If i just restart the computer start Armory and do nothing he stay connected for some hour, but when i start app he start disconnecting.
After reproduce the bug a couple of time the Wallet connection start spiking. Connect / Disconnect every 5 Sec.
Here a Link to my Full log with the Spiking bug : http://pastebin.com/e0X0Ts4w
Thanks in advance for your help
i have a bug in Armory and this is annoying cuz im just waiting for a transaction now.
Armory Version : 0.91.2 x64
Windows 7
What i see first is Armory disconnect / Reconnect every 5 second.
I check on the web and i found some people with the same issue, but in majority of time they repair it with adding memory or get a faster hard drive.
In my case its not the problem, i have 32Go of Ram and two SSD Hard-drive in RAID 1.
When i check the log file this is an example of what is see :
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync
2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Offline"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync
2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Offline"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5672 - Dashboard switched to fully-online mode
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4928 - Switching Armory functional mode to "Online"
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-06-25 23:02 (INFO) -- ArmoryQt.py:5552 - Dashboard switched to auto-InitSync
2014-06-25 23:02 (WARNING) -- ArmoryQt.py:4919 - Called updateSyncProgress while not sync'ing
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon
2014-06-25 23:02 (INFO) -- ArmoryQt.py:4986 - Switching Armory state text to Mgmt:Auto, Stat
So i tried a couple of thing to try to understand the bug, but this just give me more question
When i reboot my computer and just run Armory everything working fine.
But if i start Google Chrome and go On Gmail, Armory Disconnect
I do not understand but i can reproduce the bug like that.
Link: http://youtu.be/Q8Vve_VbvL8
The wallet don't disconnect only on Gmail, this is just an example. When i have a lot of program open the wallet bug to.
If i just restart the computer start Armory and do nothing he stay connected for some hour, but when i start app he start disconnecting.
After reproduce the bug a couple of time the Wallet connection start spiking. Connect / Disconnect every 5 Sec.
Here a Link to my Full log with the Spiking bug : http://pastebin.com/e0X0Ts4w
Thanks in advance for your help
Sounds like a connectivity issue with BitcoinQt. Add this to your bitcoin.conf, see if that helps
Code:
addnode=127.0.0.1
where can i set the location of the f.... 20 GB blockchain that the armory downloads?
if it is not possible to set it then i wont use Armory ( i have no space on my windows partition so the default path Appdata/roaming/armory is not good for me and many others )
if it is not possible to set it then i wont use Armory ( i have no space on my windows partition so the default path Appdata/roaming/armory is not good for me and many others )
Backing up a bit, it's important to understand that the blockchain files are the ones used by Bitcoin Core/bitcoind. Armory just uses a database on top of the blockchain files. I say all this just so that we're all on the same page.
Anyway, yes, it should be possible to do what you need. For the blockchain, you'll have to fire up BC Core/bitcoind. (I'm not aware of any way that Armory can do this for you.) https://en.bitcoin.it/wiki/Running_Bitcoin has info on command line arguments that let you customize where files go. In particular, the -datadir option is what you want (e.g., Bitcoin-Qt -datadir="path/to/blockchain/files").
Armory works in a similar mannet. At the command line, you can use the --dbdir option (e.g., python ArmoryQt.py --dbdir="path/to/DB/dir") to specify a different location for the database files. Just remember that, in both cases, you'll have to specify the locations every time you fire them up, otherwise you'll get errors.
Quote
and why cant use the armory the same downloaded blockchain (i can set its location) that bitcoinqt uses /(dowloaded) ?
Armory uses a database on top of the blockchain. Before the database was added, the online version of Armory used a ridiculous amount of memory (8+ GB). It's all a tradeoff in order to get the extra features provided by Armory. We're continuing to look into ways to reduce the storage footprint.
where can i set the location of the f.... 20 GB blockchain that the armory downloads?
if it is not possible to set it then i wont use Armory ( i have no space on my windows partition so the default path Appdata/roaming/armory is not good for me and many others )
and why cant use the armory the same downloaded blockchain (i can set its location) that bitcoinqt uses /(dowloaded) ?
if it is not possible to set it then i wont use Armory ( i have no space on my windows partition so the default path Appdata/roaming/armory is not good for me and many others )
and why cant use the armory the same downloaded blockchain (i can set its location) that bitcoinqt uses /(dowloaded) ?
Jump to: