Debian 9 as VM, running npm start makes it all "freeze" but...

[THeStigh]

@mykle1

If there is any excuse… It’s 03:30 AM.

But still; the config.js in the Debian 9 installation is clean, it is default.
So that is not the issue (regarding the message you pasted; that is for me running Linux through Windows :) )

[Mykle1]

@thestigh said in Debian 9 as VM, running npm start makes it all "freeze" but...:

Again, can this be a VM and/or 64 bit issue?

I’ve never used a VM environment. I strictly run ubuntu on all my machines except for 1 Pi mirror It’s definitely NOT a 64 bit issue.

[Mykle1]

@thestigh said in Debian 9 as VM, running npm start makes it all "freeze" but...:

But still; the config.js in the Debian 9 installation is clean, it is default.

You copied and renamed it?

So that is not the issue (regarding the message you pasted; that is for me running Linux through Windows )

I don’t know about running Linux through windows because I don’t do that.

[Mykle1]

@thestigh said in Debian 9 as VM, running npm start makes it all "freeze" but...:

f there is any excuse… It’s 03:30 AM.

Go to sleep. This will all be here tomorrow. I promise. :-)

[THeStigh]

@mykle1 Could it be the output is wrong? Meaning - trying to output to a different display?

[A Former User]

@thestigh
I’m not sure this is exact solution. However,
Some system (like ATB) has an issue to execute Electron of MM (after 2.x - new GPU acceleration).
You can run MM as serveronly mode to use your existing Chrome Browser instead Electron.
You can make a script to execute MM serveronly mode and Chrome to display it.

Or you can try this to disable GPU.

npm start -- --disable-gpu