vaibhav-sidapara / vagrant-manager Goto Github PK

Hello,

I get an error shown in the attached image below when starting the app.
Below is my environment:

• Using Linux Mint 18.1 Serena.
• Virtualbox installed.
• Vagrant installed.
• No vagrant boxes created yet.

Appreciate a quick response.

Cheers!

Hi!

I'm just testing out some electron apps, and yours seemed quite useful for me, I downloaded the last available portable version but sadly is not working for me. I've tried other electron apps and they seem to be working fine. Here some of my data:

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

uname -a
Linux XXXXXXX 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

vagrant -v
Vagrant 1.8.6

Expected

For the program to run when executed

Result

Running ./vagrant-manager shows absolutely nothing.
Double clicking on the same executable from GUI does nothing either.

Very nice repos btw, good job ;)
I tried it and I think the way it gets the box names is kind of wrong and for some reason, it seems to get the wrong box status from the vms. See the following screenshot;

In fact, I only have one vagrant vm running right now, but many of them are marked as status running (green icon).

I'm on latest commit 2d82e9b

I may have a look at the code later and see how this could be improved :)

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 silly lifecycle [email protected]prestart: no script for prestart, continuing
7 info lifecycle [email protected]start: [email protected]
8 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]start: PATH: /usr/share/npm/bin/node-gyp-bin:/home/user/vagrant-manager/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
10 verbose lifecycle [email protected]start: CWD: /home/user/vagrant-manager
11 silly lifecycle [email protected]start: Args: [ '-c', 'electron index.js' ]
12 info lifecycle [email protected]start: Failed to exec start script
13 verbose stack Error: [email protected] start: electron index.js
13 verbose stack spawn ENOENT
13 verbose stack at ChildProcess. (/usr/share/npm/lib/utils/spawn.js:17:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/user/vagrant-manager
16 error Linux 4.15.0-29-generic
17 error argv "/usr/bin/node" "/usr/bin/npm" "start"
18 error node v8.10.0
19 error npm v3.5.2
20 error file sh
21 error code ELIFECYCLE
22 error errno ENOENT
23 error syscall spawn
24 error [email protected] start: electron index.js
24 error spawn ENOENT
25 error Failed at the [email protected] start script 'electron index.js'.
25 error Make sure you have the latest version of node.js and npm installed.
25 error If you do, this is most likely a problem with the vagrant-manager package,
25 error not with npm itself.
25 error Tell the author that this fails on your system:
25 error electron index.js
25 error You can get information on how to open an issue for this project with:
25 error npm bugs vagrant-manager
25 error Or if that isn't available, you can get their info via:
25 error npm owner ls vagrant-manager
25 error There is likely additional logging output above.