search

iotaledger / legacy-wallet-use-trinity-wallet-instead

IOTA Wallet
GNU General Public License v3.0
2.07k stars 413 forks source link

Ubuntu 17.10 ― ENOENT during 'npm install' step #908

Open kennystrawnmusic opened 6 years ago

kennystrawnmusic commented 6 years ago

npm ERR! Linux 4.13.0-16-generic npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! node v6.11.4 npm ERR! npm v3.5.2 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! iota@2.5.6 postinstall: electron-builder install-app-deps && node install-deps.js && cd app && bower install && cd ../ui && bower install npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the iota@2.5.6 postinstall script 'electron-builder install-app-deps && node install-deps.js && cd app && bower install && cd ../ui && bower install'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the iota package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! electron-builder install-app-deps && node install-deps.js && cd app && bower install && cd ../ui && bower install npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs iota npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls iota npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /home/strawn_04/wallet/npm-debug.log

I attached a copy of npm-debug.log for further analysis. After having followed all previous steps in order including compiling the IRI and placing the iri.jar file where it belongs, getting an error like this is bizarre to say the least.

npm-debug.log

kennystrawnmusic commented 6 years ago

Installed electron-builder and docker to see if that makes a difference ― it doesn't.

kennystrawnmusic commented 6 years ago

Okay, after making sure that all the dependencies were installed and then deleting and redownloading the directories it finally managed to install successfully. Now it's time to make sure that it works properly, because there was an "invalid-meta" error thrown stating that something cannot contain minified files with one of the dependencies.

kennystrawnmusic commented 6 years ago

Update: "error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory" on "npm start" attempt

Reopening

dennym commented 6 years ago

What is the output of find /usr/lib|grep libgconf? What architecture is your linux?

geekdenz commented 6 years ago

Hi, I seem to have the same or similar problem:

`find /usr/lib|grep libgconf

/usr/lib/x86_64-linux-gnu/libgconf-2.so.4 /usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so /usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-xml.so /usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-oldxml.so /usr/lib/x86_64-linux-gnu/libgconf-2.so.4.1.5`