MagicMirror is Failing to start at all

sdetweil

@Sampleswow can you show the output of

node -v

Sampleswow

@sdetweil
pi@raspberrypi:~ $ node -v
v24.4.1
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ node -v
v24.4.1

sdetweil

@Sampleswow thanks

Try this

sudo n 22.14
hash -r
node -v

You should get 22.14 or 22.15

Then try npm start in the MagicMirror folder

Sampleswow

@sdetweil
pi@raspberrypi:~ $ sudo n 22.14
copying : node/22.14.0
installed : v22.14.0 (with npm 10.9.2)
pi@raspberrypi:~ $ hash -r
pi@raspberrypi:~ $ node -v
v22.14.0
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.32.0 start
node --run start:x11

node: bad option: --run
pi@raspberrypi:~/MagicMirror $

sdetweil

@karsten13 have any debug advice here?

karsten13

@sdetweil

can you see what I’m doing right now ;)

I used my containers a few minutes ago to see if I can reproduce but I can’t. So no idea.

sdetweil

@Sampleswow ok, it makes no sense

I would suggest starting over
Reflash the SD card
Use the script to Install

Sampleswow

@sdetweil
is that the only way? I have a lot of setup, I would hate to lose by starting over.

also again What script i have no idea what your referring to, or how to use it. I am a basic user of Magic Mirror

sdetweil

@Sampleswow

I have two sets of scripts, install/update are listed in the MagicMirror doc

Install/upgrade
https://github.com/sdetweil/MagicMirror_scripts

Backup/restore, which can save your MagicMirror setup and place it in a GitHub repo, with versions (it does not backup folders, only info required to restore the config onto a new MagicMirror install.).

https://github.com/sdetweil/MagicMirror-backup-restore

You can backup Your config now, copy off system, upload to GitHub as part of backup
config.js, custom.css, all the installed modules and where they came from. And any new files they created

I always recommend using a new SD card anyhow, just in case there is something (which I will fix)

Nodejs is just a tool we use to launch Our app, and run our code.
I don’t see any reports of problems like this do I don’t know

KristjanESPERANTO

If --run is a bad option let’s try run the long command directly and see what happens.

So instead of npm run, try this:

On Wayland:

WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland

On X11:
DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

This may show us the real core of the problem, or it works and starts MM properly and we could make it a little more comfortable (even if it is a bit hacky).