Is there something to help with this install/run? about photo-booth HOT 12 CLOSED

Hi @philipptrenz,
Sorry for my delay, I did not have a lot of time to test with Chrismas and the New year.

I have remove node-modules folder and did the complete re-install of the project and it works fine!

thanks for your software and your help

from photo-booth.

... same for me. After deleting the folder and a re-install it worked !
Thank you!

from photo-booth.

In which platform? Try running npm install again.

from photo-booth.

Hi Philipp, i appear to run into the same issue -
New Raspberry Pi 3B+ running Rasbian Stretch, (release 2018-11-13, kernel 4.14)

Nothing installed on the fresh image, just ran down your installation page one at a time and it errors on the electron-rebuild during npm install

here's the log file from the failed build -> http://termbin.com/k3p0

from photo-booth.

Hi @Widzwill thanks for providing the log file. For some reason, electron-rebuild expectes to have a more recent version of Node and npm now. Please remove node and npm and reinstall it with this script to get node v10.
The easiest way is to delete the repo and re-clone it. Then do a git checkout dev to get to the dev branch and follow the instructions inside the local README.md. Unfortunately, I currently have no hardware set at hand, so I can't test the configuration in advance. So please report the result ;)
Thanks!

from photo-booth.

Hi @csicat and @Widzwill, I have another idea where the error could come from.
Can you please change line 12 in package.json from "postinstall": "electron-rebuild" to "postinstall":"./node_modules/.bin/electron-rebuild" and redo npm install?
If this fixes your issue please report it here so I can apply the changes to the repository.

from photo-booth.

Hi @philipptrenz, I have the same issue on my rasberry pie.
I try your last post, it work during the npm install but I have the issue when I start npm

below the log:

0 info it worked if it ends with ok
1 verbose cli [ '/opt/nodejs/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 @philipptrenz/[email protected]prestart: @philipptrenz/[email protected]
6 info lifecycle @philipptrenz/[email protected]start: @philipptrenz/[email protected]
7 verbose lifecycle @philipptrenz/[email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle @philipptrenz/[email protected]start: PATH: /opt/nodejs/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/photo-booth/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle @philipptrenz/[email protected]start: CWD: /home/pi/photo-booth
10 silly lifecycle @philipptrenz/[email protected]start: Args: [ '-c', 'electron .' ]
11 info lifecycle @philipptrenz/[email protected]~start: Failed to exec start script
12 verbose stack Error: @philipptrenz/[email protected] start: electron .
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/opt/nodejs/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:180:13)
12 verbose stack at maybeClose (internal/child_process.js:936:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
13 verbose pkgid @philipptrenz/[email protected]
14 verbose cwd /home/pi/photo-booth
15 verbose Linux 4.14.79-v7+
16 verbose argv "/opt/nodejs/bin/node" "/usr/bin/npm" "start"
17 verbose node v9.11.2
18 verbose npm v5.6.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error @philipptrenz/[email protected] start: electron .
23 error spawn ENOENT
24 error Failed at the @philipptrenz/[email protected] start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

from photo-booth.

Hi @Elsurimi
thanks for your feedback. Please try to also replace "start": "electron .", with "start": "./node_modules/.bin/electron .",.
I suspect that globally linking the binaries in newer versions of Raspbian will not work for some reason ...

from photo-booth.

I updated the repository to provide these relative paths for the "postinstall" and "start" goals, so you can do a git pull and try if it fixes this issue.

from photo-booth.

Hi @philipptrenz Thanks for your quick feedback.
I downloaded your last version. I still have the same issue:

0 info it worked if it ends with ok
1 verbose cli [ '/opt/nodejs/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 @philipptrenz/[email protected]prestart: @philipptrenz/[email protected]
6 info lifecycle @philipptrenz/[email protected]start: @philipptrenz/[email protected]
7 verbose lifecycle @philipptrenz/[email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle @philipptrenz/[email protected]start: PATH: /opt/nodejs/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/photo-booth/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle @philipptrenz/[email protected]start: CWD: /home/pi/photo-booth
10 silly lifecycle @philipptrenz/[email protected]start: Args: [ '-c', 'electron .' ]
11 info lifecycle @philipptrenz/[email protected]~start: Failed to exec start script
12 verbose stack Error: @philipptrenz/[email protected] start: electron .
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/opt/nodejs/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:180:13)
12 verbose stack at maybeClose (internal/child_process.js:936:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
13 verbose pkgid @philipptrenz/[email protected]
14 verbose cwd /home/pi/photo-booth
15 verbose Linux 4.14.79-v7+
16 verbose argv "/opt/nodejs/bin/node" "/usr/bin/npm" "start"
17 verbose node v9.11.2
18 verbose npm v5.6.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error @philipptrenz/[email protected] start: electron .
23 error spawn ENOENT
24 error Failed at the @philipptrenz/[email protected] start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

from photo-booth.

from photo-booth.

Hi Philipp,

although I just started to install your Software today from the beginning I get the same issues. Did you find the mistake already?

Greetings,

Julius

from photo-booth.