Title: Armory won't start Post by: pimd on June 07, 2017, 02:49:53 PM I was running Armory 0.95.1 in a Linux Mint virtual machine. Works very well.
But version 0.96 won't start. Nothing happens. Installation went fine. At least there were no errors and Armory is showing up in the programs list. I used Armory 0.96.0 for Ubuntu/Debian 64-bit with GCC 4.7.deb. I also tried to install it on a Debian virtual machine but that didn't work out either. Does anyone knows more about this or having the same problems? And where should i find the log files? Title: Re: Armory won't start Post by: goatpig on June 07, 2017, 06:04:03 PM post logs
Title: Re: Armory won't start Post by: crabel99 on October 19, 2017, 11:22:06 PM There are no log files in .armory (ubuntu 16.04) I had the problem happen with both 0.93 and 0.93.3. Attempted to uninstall and reinstall. Dependencies checked, apt-get -f install, with the following output:
Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: python-attr python-cffi-backend python-cryptography python-enum34 python-idna python-ipaddress python-openssl python-pam python-pkg-resources python-pyasn1 python-pyasn1-modules python-serial python-service-identity python-six python-twisted python-twisted-bin python-twisted-core python-zope.interface Use 'sudo apt autoremove' to remove them. This seems odd because these were needed on the previous releases Title: Re: Armory won't start Post by: goatpig on October 20, 2017, 06:44:37 AM Run armory from the command line and post the result.
Title: Re: Armory won't start Post by: compuls1v3 on January 15, 2018, 08:09:37 PM I'm running linux mint as well and get this error when starting armory from the command line.
** (python2:4164): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-JurodTQnDt: Connection refused /home/compuls1v3 Illegal instruction Title: Re: Armory won't start Post by: droark on January 15, 2018, 08:21:39 PM Which version are you running? If you haven't already, please upgrade to 0.96.4 RC3.
Title: Re: Armory won't start Post by: compuls1v3 on January 15, 2018, 09:20:42 PM I downloaded this file armory_0.96-gcc5.4_amd64.deb . Is this the latest? Thanks for the quick reply!
Title: Re: Armory won't start Post by: PhoenixFire on January 15, 2018, 10:33:27 PM I downloaded this file armory_0.96-gcc5.4_amd64.deb . Is this the latest? Thanks for the quick reply! No.https://bitcointalk.org/index.php?topic=2754632.0 Title: Re: Armory won't start Post by: droark on January 15, 2018, 11:36:38 PM Also, while the RCs aren't posted on the website (only here), https://btcarmory.com/ is the website you should be checking.
Title: Re: Armory won't start Post by: compuls1v3 on January 17, 2018, 07:31:34 PM Sorry I'm a relatively new user to linux. I downloaded Armory 0.96.3 Ubuntu/Debian 64-bit with GCC 4.7 and the install seems to go fine now, but when I run armory from cli, I get this:
Code: compuls1v3 ~ $ armory Do I need to manually create the .bitcoin directory? Title: Re: Armory won't start Post by: droark on January 17, 2018, 07:49:29 PM Have you installed and synced Bitcoin Core?
Title: Re: Armory won't start Post by: compuls1v3 on January 17, 2018, 08:00:45 PM No I have not. Let me look into that.
Title: Re: Armory won't start Post by: droark on January 17, 2018, 11:28:46 PM Installing and syncing Core is mandatory if you wish to use Armory. You'll need ~180GB of storage on your system, and this will increase 5-10GB every month.
Title: Re: Armory won't start Post by: bob_vm on January 20, 2018, 08:06:10 PM I have Linux Mint 18.3 on 2 computers. Armory comes up normally on the newer Dell computer. I'd like to run Armory on an older HP desktop with 4GB RAM. The OS is a fairly new installation.
I installed armory_0.96-gcc5.4_amd64.deb on the HP and when I load the program, the disk starts going, but then it stops and nothing appears. Also, when I uninstall that, it fails around 75%. I installed armory_0.96.3.992-gcc5.4_amd64.deb with the same results. I downloaded source v0.96.3.992.tar.gz from here: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.992 and uncompressed it into a directory, but couldn't run make from the root directory of the extracted files. I have gcc 5.4 on my HP Linux Mint computer. I don't want to use the late model computer because it's online everyday. Am I missing a package? How can I run make? Title: Re: Armory won't start Post by: droark on January 21, 2018, 03:53:15 AM You have to run autogen.sh and configure before running make.
Title: Re: Armory won't start Post by: bob_vm on January 21, 2018, 10:49:08 PM I think I got up to the step and made the Makefile after installing a bunch of packages.
sudo make uninstall make etc. all had error messages. Title: Re: Armory won't start Post by: droark on January 21, 2018, 11:35:48 PM Which directions are you following? What have you installed?
Title: Re: Armory won't start Post by: bob_vm on January 22, 2018, 12:07:52 AM OK, I extracted https://github.com/goatpig/BitcoinArmory/archive/v0.96.3.992.tar.gz
and looked at README.md and installed the dependencies: g++ libcrypto++-dev swig python-dev python-twisted libqtcore4 libqt4-dev python-qt4 pyqt4-dev-tools all the above installed fine. Then qt4reactor.py ... I downloaded it and extracted it. I set the environment variable to its root directory. Previously PYTHONHOME was unset even though python is on Linux Mint by default. pywin32 - did not install because it's for Windows py2exe - did not install LMDB - I see that I did not install this... Their web site looks a bit confusing... Then I ran autogen.sh It instructed me to install some other GNU programs like AutoConf and a few others. Eventually I was able to create Makefile. When I run 'sudo make uninstall' I there are some lmdb errors, so I'm working on installing lmdb installed... Title: Re: Armory won't start Post by: droark on January 22, 2018, 12:34:32 AM This file (https://github.com/goatpig/BitcoinArmory/blob/v0.96.3.992/linuxbuild/Linux_build_notes.md) would be more appropriate. (I'm in the process of updating the README, by the way. The info is a bit out-of-sync.)
Title: Re: Armory won't start Post by: bob_vm on January 22, 2018, 12:36:57 AM $ sudo make uninstall
Making uninstall in cppForSwig make[1]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Making uninstall in lmdb make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' make[2]: Nothing to be done for 'uninstall'. make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' Making uninstall in fcgi make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' make[2]: *** No rule to make target 'uninstall'. Stop. make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' Makefile:1538: recipe for target 'uninstall-recursive' failed make[1]: *** [uninstall-recursive] Error 1 make[1]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Makefile:413: recipe for target 'uninstall-recursive' failed make: *** [uninstall-recursive] Error 1 $ $ sudo make clean Making clean in cppForSwig make[1]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Making clean in lmdb make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' rm -rf .libs _libs test -z "liblmdb.la" || rm -f liblmdb.la rm -f ./so_locations rm -f *.o rm -f *.lo make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' Making clean in fcgi make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' make[2]: *** No rule to make target 'clean'. Stop. make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' Makefile:1538: recipe for target 'clean-recursive' failed make[1]: *** [clean-recursive] Error 1 make[1]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Makefile:413: recipe for target 'clean-recursive' failed make: *** [clean-recursive] Error 1 $ sudo make Making all in cppForSwig make[1]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Making all in lmdb make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' depbase=`echo mdb.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" -DPACKAGE_STRING=\"BitcoinArmory\ 0.96.3.992\" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT mdb.lo -MD -MP -MF $depbase.Tpo -c -o mdb.lo mdb.c &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: gcc -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" "-DPACKAGE_STRING=\"BitcoinArmory 0.96.3.992\"" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT mdb.lo -MD -MP -MF .deps/mdb.Tpo -c mdb.c -fPIC -DPIC -o .libs/mdb.o libtool: compile: gcc -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" "-DPACKAGE_STRING=\"BitcoinArmory 0.96.3.992\"" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT mdb.lo -MD -MP -MF .deps/mdb.Tpo -c mdb.c -o mdb.o >/dev/null 2>&1 depbase=`echo midl.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" -DPACKAGE_STRING=\"BitcoinArmory\ 0.96.3.992\" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT midl.lo -MD -MP -MF $depbase.Tpo -c -o midl.lo midl.c &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: gcc -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" "-DPACKAGE_STRING=\"BitcoinArmory 0.96.3.992\"" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT midl.lo -MD -MP -MF .deps/midl.Tpo -c midl.c -fPIC -DPIC -o .libs/midl.o libtool: compile: gcc -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" "-DPACKAGE_STRING=\"BitcoinArmory 0.96.3.992\"" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT midl.lo -MD -MP -MF .deps/midl.Tpo -c midl.c -o midl.o >/dev/null 2>&1 depbase=`echo lmdbpp.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ /bin/bash ../../libtool --tag=CXX --mode=compile g++ -std=c++11 -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" -DPACKAGE_STRING=\"BitcoinArmory\ 0.96.3.992\" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT lmdbpp.lo -MD -MP -MF $depbase.Tpo -c -o lmdbpp.lo lmdbpp.cpp &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: g++ -std=c++11 -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" "-DPACKAGE_STRING=\"BitcoinArmory 0.96.3.992\"" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT lmdbpp.lo -MD -MP -MF .deps/lmdbpp.Tpo -c lmdbpp.cpp -fPIC -DPIC -o .libs/lmdbpp.o libtool: compile: g++ -std=c++11 -DPACKAGE_NAME=\"BitcoinArmory\" -DPACKAGE_TARNAME=\"bitcoinarmory\" -DPACKAGE_VERSION=\"0.96.3.992\" "-DPACKAGE_STRING=\"BitcoinArmory 0.96.3.992\"" -DPACKAGE_BUGREPORT=\"moothecowlord@gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"bitcoinarmory\" -DVERSION=\"0.96.3.992\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSIZEOF_LONG_UNSIGNED_INT=8 -DHAVE_CXX11=1 -DHAVE_PYTHON=\"2.7\" -I. -fPIC -O2 -MT lmdbpp.lo -MD -MP -MF .deps/lmdbpp.Tpo -c lmdbpp.cpp -o lmdbpp.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CXX --mode=link g++ -std=c++11 -fPIC -O2 -o liblmdb.la mdb.lo midl.lo lmdbpp.lo libtool: link: ar cru .libs/liblmdb.a .libs/mdb.o .libs/midl.o .libs/lmdbpp.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/liblmdb.a libtool: link: ( cd ".libs" && rm -f "liblmdb.la" && ln -s "../liblmdb.la" "liblmdb.la" ) make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' Making all in fcgi make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' make[2]: *** No rule to make target 'all'. Stop. make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' Makefile:1538: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Makefile:413: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 $ sudo make install Making install in cppForSwig make[1]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Making install in lmdb make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' make[3]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/lmdb' Making install in fcgi make[2]: Entering directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' make[2]: *** No rule to make target 'install'. Stop. make[2]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig/fcgi' Makefile:1538: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/bobvm/Documents/Armory/0.96.3/BitcoinArmory-0.96.3.992/cppForSwig' Makefile:413: recipe for target 'install-recursive' failed make: *** [install-recursive] Error 1 Title: Re: Armory won't start Post by: droark on January 22, 2018, 12:43:57 AM Why are you using sudo? You shouldn't use it unless you absolutely must. Also, did you make sure to install all the package in the file I linked?
Title: Re: Armory won't start Post by: bob_vm on January 22, 2018, 02:18:01 AM Yes! That page helped, and I can load...
Thank you very much. Title: Re: Armory won't start Post by: bob_vm on January 31, 2018, 02:10:28 AM OK, it's appearing offline. How do I install Bitcoin Core as there is no button?
Use this? https://bitcoin.org/en/download Linux 64 bit, or Ubuntu process. In a video someone said use these commands (for Ubuntu): sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoind I'm currently running python 'ArmoryQt.py' to start Armory. Thanks Title: Re: Armory won't start Post by: droark on January 31, 2018, 02:22:49 AM How do I install Bitcoin Core as there is no button? Armory assumes the user is smart enough to figure this out and provides no button. That said, I suppose these instructions (https://bitcoin.org/en/full-node#linux-instructions) will work for you. Can't imagine why they would've changed recently. |