Open shortymc opened 3 years ago
OK, I think there's a few different things going on here:
npm install
fails because you don't have the libsecret-1
package installed - are you sure you have it installed from step 1?npm run buildDebian
creates a package in the dist
directory - you would then need to install that using dpkg
to run it.The npm run start
approach lets you run Min in development mode, which you probably don't want to do if you can get one of the approaches above working. But if you do want to run Min in development mode:
npm run start
doesn't pass the command line arguments through, so you need to do node_modules/.bin/electron . --no-sandbox
instead.npm run start
as root the first time, so now the files in dist
are only accessible to root. Try sudo rm -rf /var/www/html/tools/test7/min-master/dist
and then npm run start
as a regular user again.Thanks for your help ! :)
for root
node_modules/.bin/electron . --no-sandbox
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [32301:0928/030715.250087:ERROR:browser_main_loop.cc(1409)] Unable to open X display. /var/www/html/tools/test7/min-master/node_modules/electron/dist/electron exited with signal SIGSEGV
after do rm -rf /var/www/html/tools/test7/min-master/dist
after in user
npm run start
npm run start
min@1.21.0 start /var/www/html/tools/test7/min-master npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.21.0 build /var/www/html/tools/test7/min-master npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.21.0 buildMain /var/www/html/tools/test7/min-master node ./scripts/buildMain.js
internal/fs/utils.js:269 throw err; ^
Error: EACCES: permission denied, open '/var/www/html/tools/test7/min-master/main.build.js'
at Object.openSync (fs.js:462:3)
at Object.writeFileSync (fs.js:1384:35)
at buildMain (/var/www/html/tools/test7/min-master/scripts/buildMain.js:35:6)
at Object.node ./scripts/buildMain.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 buildMain script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mahel/.npm/_logs/2021-09-28T01_10_42_516Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 build: npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mahel/.npm/_logs/2021-09-28T01_10_42_668Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 start: npm run build && concurrently "npm run watch" "npm run startElectron"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-09-28T01_10_42_761Z-debug.log
1.
min@1.21.0 start /var/www/html/tools/test7/min-master npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.21.0 build /var/www/html/tools/test7/min-master npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.21.0 buildMain /var/www/html/tools/test7/min-master node ./scripts/buildMain.js
internal/fs/utils.js:269 throw err; ^
Error: EACCES: permission denied, open '/var/www/html/tools/test7/min-master/main.build.js'
at Object.openSync (fs.js:462:3)
at Object.writeFileSync (fs.js:1384:35)
at buildMain (/var/www/html/tools/test7/min-master/scripts/buildMain.js:35:6)
at Object.node ./scripts/buildMain.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 buildMain script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mahel/.npm/_logs/2021-09-28T01_10_42_516Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 build: npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mahel/.npm/_logs/2021-09-28T01_10_42_668Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 start: npm run build && concurrently "npm run watch" "npm run startElectron"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-09-28T01_10_42_761Z-debug.log
Error log 2
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle min@1.21.0~prebuild: min@1.21.0
6 info lifecycle min@1.21.0~build: min@1.21.0
7 verbose lifecycle min@1.21.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.21.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/node_modules/.bin:/usr/local/lib$
9 verbose lifecycle min@1.21.0~build: CWD: /var/www/html/tools/test7/min-master
10 silly lifecycle min@1.21.0~build: Args: [
10 silly lifecycle '-c',
10 silly lifecycle 'npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload'
10 silly lifecycle ]
11 silly lifecycle min@1.21.0~build: Returned: code: 1 signal: null
12 info lifecycle min@1.21.0~build: Failed to exec build script
13 verbose stack Error: min@1.21.0 build: npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
22 error Exit status 1
23 error Failed at the min@1.21.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Error log 3
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'start' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle min@1.21.0~prestart: min@1.21.0
6 info lifecycle min@1.21.0~start: min@1.21.0
7 verbose lifecycle min@1.21.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.21.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/node_modules/.bin:/usr/local/bin$
9 verbose lifecycle min@1.21.0~start: CWD: /var/www/html/tools/test7/min-master
10 silly lifecycle min@1.21.0~start: Args: [
10 silly lifecycle '-c',
10 silly lifecycle 'npm run build && concurrently "npm run watch" "npm run startElectron"'
10 silly lifecycle ]
11 silly lifecycle min@1.21.0~start: Returned: code: 1 signal: null
12 info lifecycle min@1.21.0~start: Failed to exec start script
13 verbose stack Error: min@1.21.0 start: npm run build && concurrently "npm run watch" "npm run startElectron"
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.npm run build && concurrently "npm run watch" "npm run startElectron"
22 error Exit status 1
23 error Failed at the min@1.21.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Thanks for your help @PalmerAL I really want to make it work.
Error: EACCES: permission denied, open '/var/www/html/tools/test7/min-master/main.build.js'
You have the same file-being-owned-by-root problem here as with the dist
folder; try sudo rm /var/www/html/tools/test7/min-master/main.build.js
and then start again.
Thanks for your help and sorry for my late response. I tried without success :
in root
npm start
min@1.21.0 start /var/www/html/tools/test7/min-master npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.21.0 build /var/www/html/tools/test7/min-master npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.21.0 buildMain /var/www/html/tools/test7/min-master node ./scripts/buildMain.js
min@1.21.0 buildBrowser /var/www/html/tools/test7/min-master node ./scripts/buildBrowser.js
min@1.21.0 buildBrowserStyles /var/www/html/tools/test7/min-master node ./scripts/buildBrowserStyles.js
min@1.21.0 buildPreload /var/www/html/tools/test7/min-master node ./scripts/buildPreload.js
[0]
[0] > min@1.21.0 watch /var/www/html/tools/test7/min-master
[0] > node ./scripts/watch.js
[0]
[1]
[1] > min@1.21.0 startElectron /var/www/html/tools/test7/min-master
[1] > electron . --development-mode
[1]
[1] [1017/052500.699498:FATAL:electron_main_delegate.cc(297)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
[1] /var/www/html/tools/test7/min-master/node_modules/electron/dist/electron exited with signal SIGTRAP
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! min@1.21.0 startElectron: electron . --development-mode
[1] npm ERR! Exit status 1
[1] npm ERR!
npm ERR! Failed at the min@1.21.0 startElectron script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1]
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR! /root/.npm/_logs/2021-10-17T03_25_00_774Z-debug.log
[1] npm run startElectron exited with code 1
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'startElectron' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestartElectron', 'startElectron', 'poststartElectron' ]
5 info lifecycle min@1.21.0~prestartElectron: min@1.21.0
6 info lifecycle min@1.21.0~startElectron: min@1.21.0
7 verbose lifecycle min@1.21.0~startElectron: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.21.0~startElectron: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/node_modules/.bin:/usr/local/lib/node_modules/n$
9 verbose lifecycle min@1.21.0~startElectron: CWD: /var/www/html/tools/test7/min-master
10 silly lifecycle min@1.21.0~startElectron: Args: [ '-c', 'electron . --development-mode' ]
11 silly lifecycle min@1.21.0~startElectron: Returned: code: 1 signal: null
12 info lifecycle min@1.21.0~startElectron: Failed to exec startElectron script
13 verbose stack Error: min@1.21.0 startElectron: electron . --development-mode
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.electron . --development-mode
22 error Exit status 1
23 error Failed at the min@1.21.0 startElectron script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
in user
npm start
min@1.21.0 start /var/www/html/tools/test7/min-master npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.21.0 build /var/www/html/tools/test7/min-master npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.21.0 buildMain /var/www/html/tools/test7/min-master node ./scripts/buildMain.js
internal/fs/utils.js:269 throw err; ^
Error: EACCES: permission denied, open '/var/www/html/tools/test7/min-master/main.build.js'
at Object.openSync (fs.js:462:3)
at Object.writeFileSync (fs.js:1384:35)
at buildMain (/var/www/html/tools/test7/min-master/scripts/buildMain.js:35:6)
at Object.node ./scripts/buildMain.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 buildMain script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mahel/.npm/_logs/2021-10-17T03_26_13_176Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 build: npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mahel/.npm/_logs/2021-10-17T03_26_13_267Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 start: npm run build && concurrently "npm run watch" "npm run startElectron"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.21.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-10-17T03_26_13_353Z-debug.log
debug log 1
/home/mahel/.npm/_logs/2021-10-17T03_26_13_176Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'buildMain' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prebuildMain', 'buildMain', 'postbuildMain' ]
5 info lifecycle min@1.21.0~prebuildMain: min@1.21.0
6 info lifecycle min@1.21.0~buildMain: min@1.21.0
7 verbose lifecycle min@1.21.0~buildMain: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.21.0~buildMain: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/node_modules/.bin:/usr/local/lib/node_modules/npm/n$
9 verbose lifecycle min@1.21.0~buildMain: CWD: /var/www/html/tools/test7/min-master
10 silly lifecycle min@1.21.0~buildMain: Args: [ '-c', 'node ./scripts/buildMain.js' ]
11 silly lifecycle min@1.21.0~buildMain: Returned: code: 1 signal: null
12 info lifecycle min@1.21.0~buildMain: Failed to exec buildMain script
13 verbose stack Error: min@1.21.0 buildMain: node ./scripts/buildMain.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.node ./scripts/buildMain.js
22 error Exit status 1
23 error Failed at the min@1.21.0 buildMain script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
debug log 2
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle min@1.21.0~prebuild: min@1.21.0
6 info lifecycle min@1.21.0~build: min@1.21.0
7 verbose lifecycle min@1.21.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.21.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/node_modules/.bin:/usr/local/lib/nodemodules/npm/node$
9 verbose lifecycle min@1.21.0~build: CWD: /var/www/html/tools/test7/min-master
10 silly lifecycle min@1.21.0~build: Args: [
10 silly lifecycle '-c',
10 silly lifecycle 'npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload'
10 silly lifecycle ]
11 silly lifecycle min@1.21.0~build: Returned: code: 1 signal: null
12 info lifecycle min@1.21.0~build: Failed to exec build script
13 verbose stack Error: min@1.21.0 build: npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
22 error Exit status 1
23 error Failed at the min@1.21.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
debug log 3
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle min@1.21.0~prestart: min@1.21.0
6 info lifecycle min@1.21.0~start: min@1.21.0
7 verbose lifecycle min@1.21.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.21.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/loc$
9 verbose lifecycle min@1.21.0~start: CWD: /var/www/html/tools/test7/min-master
10 silly lifecycle min@1.21.0~start: Args: [
10 silly lifecycle '-c',
10 silly lifecycle 'npm run build && concurrently "npm run watch" "npm run startElectron"'
10 silly lifecycle ]
11 silly lifecycle min@1.21.0~start: Returned: code: 1 signal: null
12 info lifecycle min@1.21.0~start: Failed to exec start script
13 verbose stack Error: min@1.21.0 start: npm run build && concurrently "npm run watch" "npm run startElectron"
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.npm run build && concurrently "npm run watch" "npm run startElectron"
22 error Exit status 1
23 error Failed at the min@1.21.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Thanks for your support and help :)
Best regards
Don't run as root; it won't work because of the sandbox, and you break the file permissions when you run it that way. Try this:
min-master
folder.npm start
as user.Hello, Thanks for your help and sorry for my late response.
I tried in user without success also :
5 moderate errors after install involving breaking changes. i let it like this for this test.
`npm run start
min@1.22.0 start /var/www/html/tools/test7/min-master/min2 npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
[0]
[0] > min@1.22.0 watch /var/www/html/tools/test7/min-master/min2
[0] > node ./scripts/watch.js
[0]
[1]
[1] > min@1.22.0 startElectron /var/www/html/tools/test7/min-master/min2
[1] > electron . --development-mode
[1]
[1] [10678:1103/015737.900318:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.
[1] /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/electron exited with signal SIGTRAP
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! min@1.22.0 startElectron: electron . --development-mode
[1] npm ERR! Exit status 1
[1] npm ERR!
[1] npm ERR! Failed at the min@1.22.0 startElectron script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1]
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR! /home/mahel/.npm/_logs/2021-11-03T00_57_37_984Z-debug.log
[1] [10684:0100/000000.111923:ERROR:zygote_linux.cc(646)] write: Relais bris� (pipe) (32)
[1] npm run startElectron exited with code 1
`
error log :
0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'startElectron' ] 2 info using npm@6.14.4 3 info using node@v12.22.1 4 verbose run-script [ 'prestartElectron', 'startElectron', 'poststartElectron' ] 5 info lifecycle min@1.22.0~prestartElectron: min@1.22.0 6 info lifecycle min@1.22.0~startElectron: min@1.22.0 7 verbose lifecycle min@1.22.0~startElectron: unsafe-perm in lifecycle true 8 verbose lifecycle min@1.22.0~startElectron: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/min2/node_modules/.bin:/usr/local/lib/node_modu$ 9 verbose lifecycle min@1.22.0~startElectron: CWD: /var/www/html/tools/test7/min-master/min2 10 silly lifecycle min@1.22.0~startElectron: Args: [ '-c', 'electron . --development-mode' ] 11 silly lifecycle min@1.22.0~startElectron: Returned: code: 1 signal: null 12 info lifecycle min@1.22.0~startElectron: Failed to exec startElectron script 13 verbose stack Error: min@1.22.0 startElectron:
electron . --development-mode 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:314:20) 13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:314:20) 13 verbose stack at maybeClose (internal/child_process.js:1022:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) 14 verbose pkgid min@1.22.0 15 verbose cwd /var/www/html/tools/test7/min-master/min2 16 verbose Linux 4.9.0-16-amd64 17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "startElectron" 18 verbose node v12.22.1 19 verbose npm v6.14.4 20 error code ELIFECYCLE 21 error errno 1 22 error min@1.22.0 startElectron:
electron . --development-mode 22 error Exit status 1 23 error Failed at the min@1.22.0 startElectron script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]
Thanks for your help :) Best regards
please help me !
Sorry I forgot to respond.
[1] [10678:1103/015737.900318:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.
This looks like a pretty common issue in Electron: https://github.com/electron/electron/issues/17972. I think you want to change the permissions after installing as described here:
sudo chown root /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/chrome-sandbox
chmod 4755 /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/chrome-sandbox
And then npm run start
again (make sure you're not root when you do this).
Thanks for your help I do exactly what you tell me by copy pasting your 2 lines after i log in with user i got
npm start
min@1.22.0 start /var/www/html/tools/test7/min-master/min2 npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
[1]
[1] > min@1.22.0 startElectron /var/www/html/tools/test7/min-master/min2
[1] > electron . --development-mode
[1]
[0]
[0] > min@1.22.0 watch /var/www/html/tools/test7/min-master/min2
[0] > node ./scripts/watch.js
[0]
[1] Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
[1] [7362:1127/050404.767528:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
[1] /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/electron exited with signal SIGSEGV
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! min@1.22.0 startElectron: electron . --development-mode
[1] npm ERR! Exit status 1
[1] npm ERR!
[1] npm ERR! Failed at the min@1.22.0 startElectron script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1]
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR! /home/mahel/.npm/_logs/2021-11-27T04_04_05_066Z-debug.log
[1] npm run startElectron exited with code 1
888888888888888888888888888888888888888888
error log
======================
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'startElectron' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestartElectron', 'startElectron', 'poststartElectron' ]
5 info lifecycle min@1.22.0~prestartElectron: min@1.22.0
6 info lifecycle min@1.22.0~startElectron: min@1.22.0
7 verbose lifecycle min@1.22.0~startElectron: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.22.0~startElectron: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7$
9 verbose lifecycle min@1.22.0~startElectron: CWD: /var/www/html/tools/test7/min-master/min2
10 silly lifecycle min@1.22.0~startElectron: Args: [ '-c', 'electron . --development-mode' ]
11 silly lifecycle min@1.22.0~startElectron: Returned: code: 1 signal: null
12 info lifecycle min@1.22.0~startElectron: Failed to exec startElectron script
13 verbose stack Error: min@1.22.0 startElectron: electron . --development-mode
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.electron . --development-mode
22 error Exit status 1
23 error Failed at the min@1.22.0 startElectron script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I continue to hope it will works, and hope use it
Thanks very much for your support, Best regards
[1] [7362:1127/050404.767528:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
That's kind of odd. You do have a display connected, right?
If you don't have a display, you need to setup xvfb. There's some different guides if you search for it; I'm not sure what the exact steps are.
Thanks for your help :)
Sorry for late response.
You are right i need it for a dedicated server only connected to the web and i want to acces with url:port
I've installed xvfb but i don't know use it
i see this kind of command line : sudo Xvfb :99 -nolisten tcp -fbdir /var/run there : https://qastack.fr/unix/10465/how-do-i-start-xvfb-on-startup-on-debian
npm start
min@1.22.0 start /var/www/html/tools/test7/min-master/min2 npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
[0]
[0] > min@1.22.0 watch /var/www/html/tools/test7/min-master/min2
[0] > node ./scripts/watch.js
[0]
[1]
[1] > min@1.22.0 startElectron /var/www/html/tools/test7/min-master/min2
[1] > electron . --development-mode
[1]
[1] Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
[1] [22646:1224/143128.779202:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
[1] /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/electron exited with signal SIGSEGV
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! min@1.22.0 startElectron: electron . --development-mode
[1] npm ERR! Exit status 1
[1] npm ERR!
[1] npm ERR! Failed at the min@1.22.0 startElectron script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1]
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR! /home/mahel/.npm/_logs/2021-12-24T13_31_29_286Z-debug.log
[1] npm run startElectron exited with code 1
Error log :
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'startElectron' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestartElectron', 'startElectron', 'poststartElectron' ]
5 info lifecycle min@1.22.0~prestartElectron: min@1.22.0
6 info lifecycle min@1.22.0~startElectron: min@1.22.0
7 verbose lifecycle min@1.22.0~startElectron: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.22.0~startElectron: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/min2/node_modules/.bin:/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/tools/test7/min-master/min2/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin
9 verbose lifecycle min@1.22.0~startElectron: CWD: /var/www/html/tools/test7/min-master/min2
10 silly lifecycle min@1.22.0~startElectron: Args: [ '-c', 'electron . --development-mode' ]
11 silly lifecycle min@1.22.0~startElectron: Returned: code: 1 signal: null
12 info lifecycle min@1.22.0~startElectron: Failed to exec startElectron script
13 verbose stack Error: min@1.22.0 startElectron: electron . --development-mode
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.electron . --development-mode
22 error Exit status 1
23 error Failed at the min@1.22.0 startElectron script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I trust we can do it :) Please help me !
I don't entirely know how to use xvfb, but I have two guesses:
xvfb-run (from https://gist.github.com/SantoshSrinivas79/130877925f52c8fb2557): In the Min folder:
npm run build && xvfb-run node_modules/.bin/electron .
Setting the DISPLAY variable (from https://stackoverflow.com/questions/51141037/unable-to-render-webgl-in-electron-with-xvfb): Again in the Min folder:
npm run build
Xvfb :99 -screen 0 1024x768x24 & DISPLAY=:99 node_modules/.bin/electron .
See if either of those works.
Thanks you very much for your help :)
i've tried :
1st way
$ npm run build && xvfb-run node_modules/.bin/electron .
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [5298:1228/003547.448142:ERROR:angle_platform_impl.cc(44)] Display.cpp:878 (initialize): ANGLE Display::initialize error 12289: glXQueryExtensionsString returned NULL [5298:1228/003547.448826:ERROR:gl_surface_egl.cc(780)] EGL Driver message (Critical) eglInitialize: glXQueryExtensionsString returned NULL [5298:1228/003547.449307:ERROR:gl_surface_egl.cc(1375)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type [5298:1228/003547.460466:ERROR:angle_platform_impl.cc(44)] Display.cpp:878 (initialize): ANGLE Display::initialize error 12289: glXQueryExtensionsString returned NULL [5298:1228/003547.460808:ERROR:gl_surface_egl.cc(780)] EGL Driver message (Critical) eglInitialize: glXQueryExtensionsString returned NULL [5298:1228/003547.461170:ERROR:gl_surface_egl.cc(1375)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED [5298:1228/003547.461451:ERROR:gl_initializer_linux_x11.cc(178)] GLSurfaceEGL::InitializeOneOff failed. [5298:1228/003548.470496:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [5315:1228/003548.872275:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
Xvfb :99 -screen 0 1024x768x24 & DISPLAY=:99 node_modules/.bin/electron . [1] 5696 Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [5750:1228/004832.754370:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [5785:1228/004832.828092:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
Xvfb :99 -screen 0 800x600x24 & DISPLAY=:99 node_modules/.bin/electron . [2] 5829 (EE) Fatal server error: (EE) Server is already active for display 99 If this server is no longer running, remove /tmp/.X99-lock and start again. (EE) Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [5876:1228/005205.983248:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization [5910:1228/005206.054599:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
aptitude install x11-apps xbitmaps{a} xfonts-100dpi xfonts-cyrillic xfonts-scalable
npm run build && xvfb-run node_modules/.bin/electron . npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /home/mahel/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/home/mahel/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
Debug log : 0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'build' ] 2 info using npm@6.14.4 3 info using node@v12.22.1 4 verbose config Skipping project config: /home/mahel/.npmrc. (matches userconfig) 5 verbose stack Error: ENOENT: no such file or directory, open '/home/mahel/packag$ 6 verbose cwd /home/mahel 7 verbose Linux 4.9.0-16-amd64 8 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "build" 9 verbose node v12.22.1 10 verbose npm v6.14.4 11 error code ENOENT 12 error syscall open 13 error path /home/mahel/package.json 14 error errno -2 15 error enoent ENOENT: no such file or directory, open '/home/mahel/package.json' 16 error enoent This is related to npm not being able to find a file. 17 verbose exit [ -2, true ]
npm run build npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /home/mahel/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/home/mahel/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-12-28T00_16_41_105Z-debug.log
npm run build npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /home/mahel/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/home/mahel/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
after
Xvfb :99 -screen 0 1024x768x24 & DISPLAY=:99 node_modules/.bin/electron . [1] 6637 -bash: node_modules/.bin/electron: Aucun fichier ou dossier de ce type user@server:~$ (EE) Fatal server error: (EE) Server is already active for display 99 If this server is no longer running, remove /tmp/.X99-lock and start again. (EE) ^C [1]+ Termine 1 Xvfb :99 -screen 0 1024x768x24
I continue to hope ! Thanks you for your great help and support Best regards
For the first error, try --disable-gpu
:
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu
After that:
(EE) Server is already active for display 99 If this server is no longer running, remove /tmp/.X99-lock
So you're starting an X server, but you already have one running from the first attempt. I would try what it's suggesting and remove the tmp file. Or if that doesn't work you can always reboot the server.
For the errors after that:
npm ERR! enoent ENOENT: no such file or directory, open '/home/mahel/package.json'
You're in the wrong directory, you need to cd
to the Min directory first.
Hi ! And and happy new year :) Thanks you to continue to help me I hope we will find the solution. For the second error i was also surprised because i was in the min folder and not in my personnel directory, so i don't know.
For the first error i tried in user
before reboot :
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
xvfb-run: error: Xvfb failed to start
After reboot
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [1144:0110/011747.727349:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
after exit
^C[1102:0110/012432.410953:ERROR:connection.cc(66)] X connection error received. Gdk-Message: electron: Fatal IO error 11 (Ressource temporairement non disponible) on X server :99
I want to trust we are close to make it works Maybe there is also a font problem ? Thanks you for your support ! Best Regards
Looking at the xvfb options, maybe you need to tell it to pick a server number automatically?
npm run build && xvfb-run -a node_modules/.bin/electron . --disable-gpu
The gpu_init error is strange, because that suggests that it's still trying to use the GPU even with the --disable-gpu flag. I'm not sure what's causing that.
keyboard-configuration{a} libxatracker2{a} libxvmc1{a} x11-session-utils{a} xinit{a} xorg xorg-docs-core{a} xserver-xorg xserver-xorg-input-all{a} xserver-xorg-input-libinput{a} xserver-xorg-input-wacom{a} xserver-xorg-video-all{a} xserver-xorg-video-amdgpu{a} xserver-xorg-video-ati{a} xserver-xorg-video-fbdev{a} xserver-xorg-video-intel{a} xserver-xorg-video-nouveau{a} xserver-xorg-video-qxl{a} xserver-xorg-video-radeon{a} xserver-xorg-video-vesa{a} xserver-xorg-video-vmware{a} xterm{a} xserver-xorg-core xserver-xorg-legacy libx11-dev libxext-dev
I tried in user :
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu -e
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu -e -h
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu --use-gl=swiftshader -e -h
npm run build && xvfb-run node_modules/.bin/electron . --use-gl=swiftshader -e -h
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu --use-gl=swiftshader -e -h --ignore-blanks
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu --use-gl=swiftshader -e -h --ignore-blanks --password-store=basic
last error is : Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [21216:0113/105656.894253:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
exit : ^C/var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/electron exited with signal SIGINT
All errors are the same, only numbers changes. I don't know where i can read the error logs.
I found this topics, maybe it can help us for find a solution
https://stackoverflow.com/questions/48011613/rendering-webgl-image-in-headless-chrome-without-a-gpu
https://github.com/BlackArch/blackarch-iso/pull/21/commits/88b841cd9c7c0b53645826ef471ea1d5ba58de81
Thanks you very much for your help :) Have a nice day Best regards
I don't really know at this point, sorry. I'm pretty sure the font error is unrelated; I think Chromium isn't working with XVFB somehow.
I agree those are the right packages to install, I don't see anything missing.
I found a semi-related issue here: https://github.com/cypress-io/cypress/issues/18947 that suggests deleting the cache directory (/home/<username>/.config/Min
I think) and restarting; Chromium has a "gpu cache" within that directory, so that might make a difference.
Thanks very much for all the time you already take for helping me
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu --use-gl=swiftshader -e -h --ignore-blanks --disable-software-rasterizer --headless
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
xvfb-run: error: Xvfb failed to start
npm start
min@1.22.0 start /var/www/html/tools/test7/min-master/min2 npm run build && concurrently "npm run watch" "npm run startElectron"
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
[1]
[1] > min@1.22.0 startElectron /var/www/html/tools/test7/min-master/min2
[1] > electron . --development-mode
[1]
[0]
[0] > min@1.22.0 watch /var/www/html/tools/test7/min-master/min2
[0] > node ./scripts/watch.js
[0]
[1] Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
[1] [17992:0126/080451.542743:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
[1] /var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/electron exited with signal SIGSEGV
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! min@1.22.0 startElectron: electron . --development-mode
npm ERR! Exit status 1
[1] npm ERR!
[1] npm ERR! Failed at the min@1.22.0 startElectron script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1]
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR! /home/mahel/.npm/_logs/2022-01-26T07_04_52_026Z-debug.log
[1] npm run startElectron exited with code 1
GNU nano 2.7.4 Fichier�: /home/mahel/.npm/_logs/2022-01-26T07_04_52_026Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'startElectron' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestartElectron', 'startElectron', 'poststartElectron' ]
5 info lifecycle min@1.22.0~prestartElectron: min@1.22.0
6 info lifecycle min@1.22.0~startElectron: min@1.22.0
7 verbose lifecycle min@1.22.0~startElectron: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.22.0~startElectron: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifec$
9 verbose lifecycle min@1.22.0~startElectron: CWD: /var/www/html/tools/test7/min-master/min2
10 silly lifecycle min@1.22.0~startElectron: Args: [ '-c', 'electron . --development-mode' ]
11 silly lifecycle min@1.22.0~startElectron: Returned: code: 1 signal: null
12 info lifecycle min@1.22.0~startElectron: Failed to exec startElectron script
13 verbose stack Error: min@1.22.0 startElectron: electron . --development-mode
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.electron . --development-mode
22 error Exit status 1
23 error Failed at the min@1.22.0 startElectron script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
i tried : npm run startElectron
min@1.22.0 startElectron /var/www/html/tools/test7/min-master/min2 electron . --development-mode
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
[18070:0126/080731.199946:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
/var/www/html/tools/test7/min-master/min2/node_modules/electron/dist/electron exited with signal SIGSEGV
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.22.0 startElectron: electron . --development-mode
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the min@1.22.0 startElectron script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2022-01-26T07_07_31_476Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'startElectron' ]
2 info using npm@6.14.4
3 info using node@v12.22.1
4 verbose run-script [ 'prestartElectron', 'startElectron', 'poststartElectron' ]
5 info lifecycle min@1.22.0~prestartElectron: min@1.22.0
6 info lifecycle min@1.22.0~startElectron: min@1.22.0
7 verbose lifecycle min@1.22.0~startElectron: unsafe-perm in lifecycle true
8 verbose lifecycle min@1.22.0~startElectron: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifec$
9 verbose lifecycle min@1.22.0~startElectron: CWD: /var/www/html/tools/test7/min-master/min2
10 silly lifecycle min@1.22.0~startElectron: Args: [ '-c', 'electron . --development-mode' ]
11 silly lifecycle min@1.22.0~startElectron: Returned: code: 1 signal: null
12 info lifecycle min@1.22.0~startElectron: Failed to exec startElectron script
13 verbose stack Error: min@1.22.0 startElectron: electron . --development-mode
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.electron . --development-mode
22 error Exit status 1
23 error Failed at the min@1.22.0 startElectron script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Thanks you very much for your help Best Regards
hi :) I advanced a little bit !
i tried : npm install xvfb install fine but nothing changes npm install xvfb-maybe install fine but not works
$ xvfb-run -e /dev/stdout -s '-screen 0 1024x768x24' node_modules/.bin/electron . --disable-gpu
(EE)
Fatal server error:
(EE) Server is already active for display 99
If this server is no longer running, remove /tmp/.X99-lock
and start again.
(EE)
xvfb-run: error: Xvfb failed to start
$ xvfb-run -e /dev/stdout -s '-screen 0 1024x768x24' node_modules/.bin/electron . --disable-gpu _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) xvfb-run: error: Xvfb failed to start
AFTER REMOVING "/tmp/.X99-lockold" and "/tmp/.X11-unix/X99"
$ xvfb-run -e /dev/stdout -s '-screen 0 1024x768x24' node_modules/.bin/electron . --disable-gpu _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) xvfb-run: error: Xvfb failed to start $ xvfb-run -e /dev/stdout -s '-screen 0 1024x768x24' node_modules/.bin/electron . --disable-gpu _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) xvfb-run: error: Xvfb failed to start
AFTER aptitude install libxxf86dga-dev x11proto-xf86dga-dev
I'm trying to know if xorg is already running
$ ps -C Xorg
Result
PID TTY TIME CMD
i can't understand if it's already running
Also i see many files (attempts ?) in folders called xvfb-run.4cMhGZ or other suffix inside /tmp/ folder each folders contain a file called Xautority i can't see all characters with my editor
So i'm blocked ad this point.
After reboot, the error is come back
xvfb-run -e /dev/stdout -s '-screen 0 1024x768x24' node_modules/.bin/electron . --disable-gpu Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" [874:0130/053838.855984:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
xvfb-run -e /dev/stdout -s '-screen 0 1024x768x24' node_modules/.bin/electron . --disable-gpu [1237:0130/054624.386670:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
and
npm run build && xvfb-run node_modules/.bin/electron . --disable-gpu --use-gl=swiftshader -e -h --ignore-blanks --disable-software-rasterizer --headless
min@1.22.0 build /var/www/html/tools/test7/min-master/min2 npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
min@1.22.0 buildMain /var/www/html/tools/test7/min-master/min2 node ./scripts/buildMain.js
min@1.22.0 buildBrowser /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowser.js
min@1.22.0 buildBrowserStyles /var/www/html/tools/test7/min-master/min2 node ./scripts/buildBrowserStyles.js
min@1.22.0 buildPreload /var/www/html/tools/test7/min-master/min2 node ./scripts/buildPreload.js
[1479:0130/055501.330174:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is disabled, ANGLE is
Please help me !
Best regards
Hi, I'm continue looking for a solution. Have you got a new idea for make it work ?
Best regards
Hello
I found something maybe help us to find a solution
https://www.electronjs.org/docs/v14-x-y/api/app#appdisablehardwareacceleration
this is a way ?
source : https://stackoverflow.com/questions/70267992/win10-electron-error-passthrough-is-not-supported-gl-is-disabled-angle-is Do you know if i can apply it for min browser ?
Thanks very much for your hep
Best regards
Hi, I don't have any new ideas, sorry.
disableHardwareAcceleration()
should do the same thing as launching Min with the --disable-gpu
flag. If you want to try adding that, you can insert it here: https://github.com/minbrowser/min/blob/master/main/main.js#L17, and recompiling using these instructions: https://github.com/minbrowser/min#developing. But I wouldn't expect it to make a difference, since you tried the flag already.
So i was make a special dedicated server (whith xvfb succesfully installed) for making it work, but my neighbor don't known nothing at informatics throw it in a garbage by mistake :,-( i'm cryiiing !!) so i will try mount a new web server with another graphic card and i hope it will found is place in the datacenter i want with min browser working on it for serve webpages through my website. I need your help, i will come back when xvfb or another tricks is working. I'm sure we can do it with Debian.
i tried to install it with deb but how get it in the browser ? I install many dependancies of kde but i want access from the web and its not working
--------dpkg -i min_1.21.0_amd64.debSélection du paquet min précédemment désélectionné. (Lecture de la base de données... 127522 fichiers et répertoires déjà installés.) Préparation du dépaquetage de min_1.21.0_amd64.deb ... Dépaquetage de min (1.21.0) ... dpkg: des problèmes de dépendances empêchent la configuration de min : min dépend de libnotify4 ; cependant : Le paquet libnotify4 n'est pas installé. min dépend de libnss3 ; cependant : Le paquet libnss3 n'est pas installé. min dépend de kde-cli-tools | kde-runtime | trash-cli | libglib2.0-bin | gvfs-bin ; cependant : Le paquet kde-cli-tools n'est pas installé. Le paquet kde-runtime n'est pas installé. Le paquet trash-cli n'est pas installé. Le paquet libglib2.0-bin n'est pas installé. Le paquet gvfs-bin n'est pas installé. min dépend de libsecret-1-dev ; cependant : Le paquet libsecret-1-dev n'est pas installé.
dpkg: erreur de traitement du paquet min (--install) : problèmes de dépendances - laissé non configuré Traitement des actions différées (« triggers ») pour mime-support (3.60) ... Des erreurs ont été rencontrées pendant l'exécution : min Vous avez du nouveau courrier dans /var/mail/root root@srv132:/var/www/html/tools/test7/min-master# aptitude install libnotify4 libnss3 kde-cli-tools-kde-runtime trash-cli libglib2.0-bin gvfs-bin libsecret-1-dev Impossible de trouver un paquet dont le nom ou la description corresponde à « kde-cli-tools-kde-runtime » Unable to apply some actions, aborting
after
aptitude install libnotify4 libnss3 kde-cli-tools kde-runtime trash-cli libglib2.0-bin gvfs-bin libsecret-1-dev Les NOUVEAUX paquets suivants vont être installés :
aspell{a} aspell-en{a} dbus-x11{a} desktop-file-utils{a} dictionaries-common{a} docbook-xml{a} docbook-xsl{a} dosfstools{a} eject{a} emacsen-common{a} enchant{a} exfat-fuse{a} exfat-utils{a} fuse{a} gdisk{a} gir1.2-secret-1{a} gstreamer1.0-alsa{a} gstreamer1.0-plugins-good{a} gstreamer1.0-pulseaudio{a} gstreamer1.0-x{a} gvfs{a} gvfs-bin gvfs-common{a} gvfs-daemons{a} gvfs-libs{a} hunspell-en-us{a} icoutils{a} kate-data{a} katepart{a} kde-cli-tools kde-cli-tools-data{a} kde-runtime kde-runtime-data{a} kdelibs-bin{a} kdelibs5-data{a} kdelibs5-plugins{a} kdoctools{a} kio{a} kpackagelauncherqml{a} kpackagetool5{a} libasound2-plugins{a} libaspell15{a} libatasmart4{a} libattica0.4{a} libaudio2{a} libbasicusageenvironment1{a} libbluray1{a} libcanberra-pulse{a} libcanberra0{a} libcddb2{a} libclucene-core1v5{a} libdbusmenu-qt2{a} libdbusmenu-qt5-2{a} libdlrestrictions1{a} libdvbpsi10{a} libebml4v5{a} libenchant1c2a{a} libexiv2-14{a} libfam0{a} libgck-1-0{a} libgcr-3-common{a} libgcr-base-3-1{a} libgles2-mesa{a} libglib2.0-bin libglib2.0-dev{a} libgpgme++2v5{a} libgpgmepp6{a} libgroupsock8{a} libhunspell-1.4-0{a} libilmbase12{a} libimobiledevice6{a} libiodbc2{a} libkactivities6{a} libkatepartinterfaces4{a} libkcmutils4{a} libkde3support4{a} libkdeclarative5{a} libkdecore5{a} libkdesu5{a} libkdeui5{a} libkdewebkit5{a} libkdnssd4{a} libkemoticons4{a} libkf5archive5{a} libkf5attica5{a} libkf5auth-data{a} libkf5auth5{a} libkf5bookmarks-data{a} libkf5bookmarks5{a} libkf5codecs-data{a} libkf5codecs5{a} libkf5completion-data{a} libkf5completion5{a} libkf5config-bin{a} libkf5config-data{a} libkf5configcore5{a} libkf5configgui5{a} libkf5configwidgets-data{a} libkf5configwidgets5{a} libkf5coreaddons-data{a} libkf5coreaddons5{a} libkf5crash5{a} libkf5dbusaddons-bin{a} libkf5dbusaddons-data{a} libkf5dbusaddons5{a} libkf5declarative-data{a} libkf5declarative5{a} libkf5globalaccel-bin{a} libkf5globalaccel-data{a} libkf5globalaccel5{a} libkf5globalaccelprivate5{a} libkf5guiaddons5{a} libkf5i18n-data{a} libkf5i18n5{a} libkf5iconthemes-bin{a} libkf5iconthemes-data{a} libkf5iconthemes5{a} libkf5itemviews-data{a} libkf5itemviews5{a} libkf5jobwidgets-data{a} libkf5jobwidgets5{a} libkf5kcmutils-data{a} libkf5kcmutils5{a} libkf5kdelibs4support-data{a} libkf5kdelibs4support5{a} libkf5kdelibs4support5-bin{a} libkf5kiocore5{a} libkf5kiofilewidgets5{a} libkf5kiontlm5{a} libkf5kiowidgets5{a} libkf5notifications-data{a} libkf5notifications5{a} libkf5package-data{a} libkf5package5{a} libkf5parts-data{a} libkf5parts-plugins{a} libkf5parts5{a} libkf5pty-data{a} libkf5pty5{a} libkf5quickaddons5{a} libkf5service-bin{a} libkf5service-data{a} libkf5service5{a} libkf5solid5{a} libkf5solid5-data{a} libkf5sonnet5-data{a} libkf5sonnetcore5{a} libkf5sonnetui5{a} libkf5su-bin{a} libkf5su-data{a} libkf5su5{a} libkf5textwidgets-data{a} libkf5textwidgets5{a} libkf5wallet-bin{a} libkf5wallet-data{a} libkf5wallet5{a} libkf5widgetsaddons-data{a} libkf5widgetsaddons5{a} libkf5windowsystem-data{a} libkf5windowsystem5{a} libkf5xmlgui-bin{a} libkf5xmlgui-data{a} libkf5xmlgui5{a} libkfile4{a} libkhtml5{a} libkio5{a} libkjsapi4{a} libkjsembed4{a} libkmediaplayer4{a} libknewstuff3-4{a} libknotifyconfig4{a} libkntlm4{a} libkparts4{a} libkpty4{a} libkrosscore4{a} libktexteditor4{a} libkwalletbackend5-5{a} libkxmlrpcclient4{a} liblirc-client0{a} liblivemedia57{a} libmatroska6v5{a} libmng1{a} libmtp-common{a} libmtp-runtime{a} libmtp9{a} libnepomuk4{a} libnepomukquery4a{a} libnepomukutils4{a} libnfs8{a} libnl-3-200{a} libnl-route-3-200{a} libnotify4 libnspr4{a} libnss3 libntfs-3g871{a} libntrack-qt4-1{a} libntrack0{a} libopenexr22{a} libopenmpt-modplug1{a} libparted2{a} libpcre3-dev{a} libpcre32-3{a} libphonon4{a} libphonon4qt5-4{a} libplasma3{a} libplist3{a} libpolkit-agent-1-0{a} libpolkit-backend-1-0{a} libpolkit-gobject-1-0{a} libpolkit-qt-1-1{a} libpolkit-qt5-1-1{a} libprotobuf-lite10{a} libproxy-tools{a} libpulse-mainloop-glib0{a} libpulsedsp{a} libqca2{a} libqca2-plugins{a} libqt4-dbus{a} libqt4-declarative{a} libqt4-designer{a} libqt4-network{a} libqt4-opengl{a} libqt4-qt3support{a} libqt4-script{a} libqt4-sql{a} libqt4-sql-mysql{a} libqt4-svg{a} libqt4-xml{a} libqt4-xmlpatterns{a} libqt5quickwidgets5{a} libqt5script5{a} libqt5test5{a} libqt5x11extras5{a} libqt5xml5{a} libqtcore4{a} libqtdbus4{a} libqtgui4{a} libqtwebkit4{a} libresid-builder0c2a{a} libsdl-image1.2{a} libsdl1.2debian{a} libsecret-1-0{a} libsecret-1-dev libsecret-common{a} libsidplay2{a} libsolid4{a} libsoprano4{a} libspeexdsp1{a} libssh-gcrypt-4{a} libtag1v5{ab} libtag1v5-vanilla{ab} libthreadweaver4{a} libudisks2-0{a} libupnp6{a} libupower-glib3{a} libusageenvironment3{a} libusbmuxd4{a} libutempter0{a} libvlc-bin{a} libvlc5{a} libvlccore9{a} libwebrtc-audio-processing1{a} libx264-148{a} libx265-95{a} libxcb-xv0{a} libxml2-utils{a} notification-daemon{a} ntfs-3g{a} ntrack-module-libnl-0{a} oxygen-icon-theme{a} parted{a} phonon{a} phonon-backend-gstreamer{a} phonon-backend-gstreamer-common{a} phonon4qt5{a} phonon4qt5-backend-vlc{a} plasma-scriptengine-javascript{a} policykit-1{a} pulseaudio{a} pulseaudio-utils{a} qdbus{a} qt-at-spi{a} qtchooser{a} qtcore4-l10n{a} rtkit{a} sgml-data{a} sonnet-plugins{a} soprano-daemon{a} sound-theme-freedesktop{a} trash-cli udisks2{a} upower{a} usbmuxd{a} vlc-data{a} vlc-plugin-base{a} vlc-plugin-video-output{a} zlib1g-dev{a} Les paquets partiellement installés suivants seront configurés : min 0 paquets mis à jour, 297 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de télécharger 133 Mo/135 Mo d'archives. Après dépaquetage, 461 Mo seront utilisés. Les paquets suivants ont des dépendances non satisfaites : libtag1v5 : Est en conflit avec: libtag1c2a but 1.9.1-2.1+deb8u1 is installed libtag1v5-vanilla : Casse: libtag1-vanilla but 1.9.1-2.1+deb8u1 is installed Les actions suivantes permettront de résoudre ces dépendances :
1) gstreamer0.10-plugins-good [0.10.31-3+nmu4+deb8u3 (now)] 2) libtag1-vanilla [1.9.1-2.1+deb8u1 (now)]
3) libtag1c2a [1.9.1-2.1+deb8u1 (now)]
Accepter cette solution ? [Y/n/q/?] y
after install ok but not acces from the web
After try npm install
i tried to install with npm npm update :
npm update
prebuild-install WARN install libsecret-1.so.0: cannot open shared object file: No such file or directory
Package libsecret-1 was not found in the pkg-config search path. Perhaps you should add the directory containing
libsecret-1.pc' to the PKG_CONFIG_PATH environment variable No package 'libsecret-1' found gyp: Call to 'pkg-config --libs-only-l libsecret-1' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error:
gypfailed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:314:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12) gyp ERR! System Linux 4.9.0-16-amd64 gyp ERR! command "/usr/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /var/www/html/tools/test7/min-master/node_modules/keytar gyp ERR! node -v v12.22.1 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! keytar@7.6.0 build:
node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the keytar@7.6.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm WARN Local package.json exists, but node_modules missing, did you mean to install?npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-09-27T01_40_41_490Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! keytar@7.6.0 install:
prebuild-install || npm run build
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the keytar@7.6.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-09-27T01_40_42_484Z-debug.log root@srv132:/var/www/html/tools/test7/min-master# wget https://github.com/minbrowser/min/releases/download/v1.21.0/min_1.21.0_amd64.deb --2021-09-27 04:08:04-- https://github.com/minbrowser/min/releases/download/v1.21.0/min_1.21.0_amd64.deb Résolution de github.com (github.com)… 140.82.121.3 Connexion à github.com (github.com)|140.82.121.3|:443… connecté. requête HTTP transmise, en attente de la réponse… 302 Found Emplacement : https://github-releases.githubusercontent.com/45319761/46677692-b416-4095-9fc2-43bb46e5fb3b?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210927%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210927T020805Z&X-Amz-Expires=300&X-Amz-Signature=278997badc6d8603b919191090b5eaa6843c1fc9fb6850ec142e0712f4dc7c07&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=45319761&response-content-disposition=attachment%3B%20filename%3Dmin_1.21.0_amd64.deb&response-content-type=application%2Foctet-stream [suivant] --2021-09-27 04:08:05-- https://github-releases.githubusercontent.com/45319761/46677692-b416-4095-9fc2-43bb46e5fb3b?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210927%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210927T020805Z&X-Amz-Expires=300&X-Amz-Signature=278997badc6d8603b919191090b5eaa6843c1fc9fb6850ec142e0712f4dc7c07&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=45319761&response-content-disposition=attachment%3B%20filename%3Dmin_1.21.0_amd64.deb&response-content-type=application%2Foctet-stream Résolution de github-releases.githubusercontent.com (github-releases.githubusercontent.com)… 185.199.111.154, 185.199.109.154, 185.199.108.154, ... Connexion à github-releases.githubusercontent.com (github-releases.githubusercontent.com)|185.199.111.154|:443… connecté. requête HTTP transmise, en attente de la réponse… 200 OK Taille : 61449512 (59M) [application/octet-stream] Sauvegarde en : « min_1.21.0_amd64.deb »
min_1.21.0_amd64.deb 100%[======================>] 58,60M 14,8MB/s in 4,1s
2021-09-27 04:08:09 (14,4 MB/s) — « min_1.21.0_amd64.deb » sauvegardé [61449512/61449512]
after
npm install its ok but not working
npm install npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future npm WARN deprecated har-validator@5.1.5: this library is no longer supported
node-pre-gyp WARN Using request for node-pre-gyp https download [lzma-native] Success: "/var/www/html/tools/test7/min-master/node_modules/lzma-native/binding-v6.0.1-n-api-linux-x64/lzma_native.node" is installed via remote
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 769 packages from 516 contributors and audited 799 packages in 156.006s
79 packages are looking for funding run
npm fund
for detailsfound 0 vulnerabilities
after
npm run buildDebian
Packaging app for platform linux x64 using electron v14.0.0-beta.21 make : on entre dans le répertoire « /tmp/electron-packager/linux-x64/min-linux-x64/resources/app/node_modules/keytar/build » CXX(target) Release/obj.target/keytar/src/async.o CXX(target) Release/obj.target/keytar/src/main.o CXX(target) Release/obj.target/keytar/src/keytar_posix.o SOLINK_MODULE(target) Release/obj.target/keytar.node COPY Release/keytar.node make : on quitte le répertoire « /tmp/electron-packager/linux-x64/min-linux-x64/resources/app/node_modules/keytar/build » Creating package (this may take a while) Successfully created package.
after
root@srv132:/var/www/html/tools/test7/min-master# npm run start
[1] [1] > min@1.21.0 startElectron /var/www/html/tools/test7/min-master [1] > electron . --development-mode [1] [0] [0] > min@1.21.0 watch /var/www/html/tools/test7/min-master [0] > node ./scripts/watch.js [0] [1] [0927/045845.460710:FATAL:electron_main_delegate.cc(297)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. [1] /var/www/html/tools/test7/min-master/node_modules/electron/dist/electron exited with signal SIGTRAP [1] npm ERR! code ELIFECYCLE [1] npm ERR! errno 1 [1] npm ERR! min@1.21.0 startElectron:
electron . --development-mode
[1] npm ERR! Exit status 1 [1] npm ERR! [1] npm ERR! Failed at the min@1.21.0 startElectron script. [1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. [1] [1] npm ERR! A complete log of this run can be found in: [1] npm ERR! /root/.npm/_logs/2021-09-27T02_58_45_533Z-debug.log [1] npm run startElectron exited with code 1 ^[[A^[[A^[[B^C[0] npm run watch exited with code SIGINTroot@srv132:/var/www/html/tools/test7/min-master# npm run start --no-sandbox
[0] [0] > min@1.21.0 watch /var/www/html/tools/test7/min-master [0] > node ./scripts/watch.js [0] [1] [1] > min@1.21.0 startElectron /var/www/html/tools/test7/min-master [1] > electron . --development-mode [1] [1] [0927/050022.011878:FATAL:electron_main_delegate.cc(297)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. [1] /var/www/html/tools/test7/min-master/node_modules/electron/dist/electron exited with signal SIGTRAP [1] npm ERR! code ELIFECYCLE [1] npm ERR! errno 1 [1] npm ERR! min@1.21.0 startElectron:
electron . --development-mode
[1] npm ERR! Exit status 1 [1] npm ERR! [1] npm ERR! Failed at the min@1.21.0 startElectron script. [1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. [1] [1] npm ERR! A complete log of this run can be found in: [1] npm ERR! /root/.npm/_logs/2021-09-27T03_00_22_073Z-debug.log [1] npm run startElectron exited with code 1 ^C[0] npm run watch exited with code SIGINTafter
npm run start --no-sandbox
[0] [0] > min@1.21.0 watch /var/www/html/tools/test7/min-master [0] > node ./scripts/watch.js [0] [1] [1] > min@1.21.0 startElectron /var/www/html/tools/test7/min-master [1] > electron . --development-mode [1] [1] [0927/050943.391894:FATAL:electron_main_delegate.cc(297)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. [1] /var/www/html/tools/test7/min-master/node_modules/electron/dist/electron exited with signal SIGTRAP [1] npm ERR! code ELIFECYCLE [1] npm ERR! errno 1 [1] npm ERR! min@1.21.0 startElectron:
electron . --development-mode
[1] npm ERR! Exit status 1 [1] npm ERR! [1] npm ERR! Failed at the min@1.21.0 startElectron script. [1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. [1] [1] npm ERR! A complete log of this run can be found in: [1] npm ERR! /root/.npm/_logs/2021-09-27T03_09_43_456Z-debug.log [1] npm run startElectron exited with code 1after with a normal user
npm run start
internal/fs/utils.js:269 throw err; ^
Error: EACCES: permission denied, open '/var/www/html/tools/test7/min-master/dist/localization.build.js' at Object.openSync (fs.js:462:3) at Object.writeFileSync (fs.js:1384:35) at buildLocalization (/var/www/html/tools/test7/min-master/scripts/buildLocalization.js:60:6) at buildMain (/var/www/html/tools/test7/min-master/scripts/buildMain.js:27:36) at Object. (/var/www/html/tools/test7/min-master/scripts/buildMain.js:41:3)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) {
errno: -13,
syscall: 'open',
code: 'EACCES',
path: '/var/www/html/tools/test7/min-master/dist/localization.build.js'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! min@1.21.0 buildMain:
node ./scripts/buildMain.js
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the min@1.21.0 buildMain script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-09-27T03_02_20_655Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! min@1.21.0 build:
npm run buildMain && npm run buildBrowser && npm run buildBrowserStyles && npm run buildPreload
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the min@1.21.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-09-27T03_02_20_797Z-debug.log npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! min@1.21.0 start:
npm run build && concurrently "npm run watch" "npm run startElectron"
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the min@1.21.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/mahel/.npm/_logs/2021-09-27T03_02_20_894Z-debug.log
debug log
0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'start' ] 2 info using npm@6.14.4 3 info using node@v12.22.1 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle min@1.21.0~prestart: min@1.21.0 6 info lifecycle min@1.21.0~start: min@1.21.0 7 verbose lifecycle min@1.21.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle min@1.21.0~start: PATH: /usr/local/lib/node_modules/npm/node_mo$ 9 verbose lifecycle min@1.21.0~start: CWD: /var/www/html/tools/test7/min-master 10 silly lifecycle min@1.21.0~start: Args: [ 10 silly lifecycle '-c', 10 silly lifecycle 'npm run build && concurrently "npm run watch" "npm run startE$ 10 silly lifecycle ] 11 silly lifecycle min@1.21.0~start: Returned: code: 1 signal: null 12 info lifecycle min@1.21.0~start: Failed to exec start script 13 verbose stack Error: min@1.21.0 start:
npm run build && concurrently "npm run w$ 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/n$ 13 verbose stack at EventEmitter.emit (events.js:314:20) 13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/n$ 13 verbose stack at ChildProcess.emit (events.js:314:20) 13 verbose stack at maybeClose (internal/child_process.js:1022:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process$ 14 verbose pkgid min@1.21.0 15 verbose cwd /var/www/html/tools/test7/min-master 16 verbose Linux 4.9.0-16-amd64 17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "start" 18 verbose node v12.22.1 19 verbose npm v6.14.4 20 error code ELIFECYCLE 21 error errno 1 22 error min@1.21.0 start:
npm run build && concurrently "npm run watch" "npm run $ 22 error Exit status 1 23 error Failed at the min@1.21.0 start script. 23 error This is probably not a problem with npm. There is likely additional loggin$ 24 verbose exit [ 1, true ]Please help me !
Thanks for your support