Hi, community!
My boss wants to use q2studio in our new server (native Ubuntu 20.04). I've already installed qiime2 2020.11 via conda. I was following q2studio tutorial and I seemed to work correctly until the step or running:
npm start
/home/user/q2studio-2020.11.0/node_modules/electron/dist/electron: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! q2studio@2020.11.0 start:cross-env NODE_ENV=production electron -r babel-register build/main.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the q2studio@2020.11.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/user/.npm/_logs/2020-12-17T18_14_16_964Z-debug.log
Checking the debug log, it says:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@6.14.4
3 info using node@v10.19.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle q2studio@2020.11.0~prestart: q2studio@2020.11.0
6 info lifecycle q2studio@2020.11.0~start: q2studio@2020.11.0
7 verbose lifecycle q2studio@2020.11.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle q2studio@2020.11.0~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/user/q2studio-2020.11.0/node_modules/.bin:/home/user/miniconda3/envs/qiime2/bin:/home/user/miniconda3/bin:/home/user/miniconda3/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle q2studio@2020.11.0~start: CWD: /home/user/q2studio-2020.11.0
10 silly lifecycle q2studio@2020.11.0~start: Args: [ '-c',
10 silly lifecycle 'cross-env NODE_ENV=production electron -r babel-register build/main.js' ]
11 info lifecycle q2studio@2020.11.0~start: Failed to exec start script
12 verbose stack Error: q2studio@2020.11.0 start: `cross-env NODE_ENV=production electron -r babel-register build/main.js`
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:198:13)
12 verbose stack at maybeClose (internal/child_process.js:982:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
13 verbose pkgid q2studio@2020.11.0
14 verbose cwd /home/user/q2studio-2020.11.0
15 verbose Linux 5.4.0-58-generic
16 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
17 verbose node v10.19.0
18 verbose npm v6.14.4
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error q2studio@2020.11.0 start: `cross-env NODE_ENV=production electron -r babel-register build/main.js`
23 error spawn ENOENT
24 error Failed at the q2studio@2020.11.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
I've looking for a way to solve this (like ```
npm --version
npm install express
npm init -y
Best,
Mario.