Qiime2 Studio npm start problems

Technical Support
1

Hi!
I have problems launching Qiime2 Studio.
I have installed the qiime2 version qiime2-2020.8 and q2studio-2020.8.0 using conda.
I use MobaXterm, WSL-Ubuntu to run qiime2 studio. It has worked very well previously. But after I got a new computer and installed the new version I have problems launching the qiime 2 Studio window.

The error message after running npm start:

shared memfd open() failed: Function not implemented

The code i used:

(base) charlotte@AAS-DP1Q9Y2:~$ conda activate qiime2-2020.8
(qiime2-2020.8) charlotte@AAS-DP1Q9Y2:~$ ls
Miniconda-latest-Linux-x86_64.sh   miniconda2  q2studio-2020.6.0  qiime2-2020.6-py36-linux-conda.yml
Miniconda3-latest-Linux-x86_64.sh  miniconda3  q2studio-2020.8.0  qiime2-ecam-tutorial
(qiime2-2020.8) charlotte@AAS-DP1Q9Y2:~$ cd q2studio-2020.8.0/
(qiime2-2020.8) charlotte@AAS-DP1Q9Y2:~/q2studio-2020.8.0$ ls
LICENSE  Makefile  README.md  app  build  config  node_modules  package-lock.json  package.json  q2studio  setup.py  test
(qiime2-2020.8) charlotte@AAS-DP1Q9Y2:~/q2studio-2020.8.0$ npm start

> [email protected] start /home/charlotte/q2studio-2020.8.0
> cross-env NODE_ENV=production electron -r babel-register build/main.js

shared memfd open() failed: Function not implemented
(qiime2-2020.8) charlotte@AAS-DP1Q9Y2:~/q2studio-2020.8.0$ npm start --verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node', '/usr/local/bin/npm', 'start', '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm verb run-script [ 'prestart', 'start', 'poststart' ]
npm info lifecycle [email protected]~prestart: [email protected]
npm info lifecycle [email protected]~start: [email protected]

> [email protected] start /home/charlotte/q2studio-2020.8.0
> cross-env NODE_ENV=production electron -r babel-register build/main.js

shared memfd open() failed: Function not implemented
npm verb lifecycle [email protected]~start: unsafe-perm in lifecycle true
npm verb lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/charlotte/q2studio-2020.8.0/node_modules/.bin:/home/charlotte/miniconda2/envs/qiime2-2020.8/bin:/home/charlotte/miniconda2/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Users/CHARLO~1.NIL/AppData/Roaming/MobaXterm/slash/bin:/mnt/c/Windows:/mnt/c/Windows/System32:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/snap/bin
npm verb lifecycle [email protected]~start: CWD: /home/charlotte/q2studio-2020.8.0
npm info lifecycle [email protected]~poststart: [email protected]
npm verb exit [ 0, true ]
npm timing npm Completed in 2156ms
npm info ok

Best,
Charlotte

3

Hi @charlotte.nilsen!

It looks to me like somehow you might be using WSL 1 instead of WSL 2. I'm not sure how to check which version you have installed, but maybe you should start there.

Keep us posted! :qiime2:

5

Hi!
I don’t have access to Windows 10, v. 1903, which is needed to install WSL2.
In which q2 studio version did it change from WSL1 to WSL2? The last version I had was q2studio-2019.1, and I think I used WSL1.

Charlotte

7

Hi @charlotte.nilsen!

q2studio doesn't care (or know) about things like WSL, its just a GUI desktop app. I think the right question for you to ask is "in which version of WSL did Windows allow GUI apps?" - in which case, it looks like WSL 2 started to allow it, but even still, it isn't technically supported:

In particular, check out this part:

WSL does not aim to support GUI desktops or applications (e.g. Gnome, KDE, etc.)

Interesting! It doesn't sound like that was even technically possible, but I have never tried, so who knows.

So unfortunately I don't think there is much we can do here for you - I'm sorry! You could always try our VirtualBox image - that has q2studio baked in.

:qiime2:

9

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.