Read the statement by Michael Teeuw here.
MagicMirror is Failing to start at all
-
If
--runis 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=waylandOn X11:
DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.jsThis 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).
-
@KristjanESPERANTO said in MagicMirror is Failing to start at all:
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
This Command STARTED my Mirror!!!
Im super excited everything is the way I left it even no loading google images lol (I know i have to find and alternative now )
-
@Sampleswow awesome
edit the package.json
and change the “start”
to “startx”
then add this line after"start":"DISPLAY=${DISPLAY:=:0} ./node_modules/.bin/electron js/electron.js",then
npm startshould start your MagicMirror
this was the way it was before this release
-
@sdetweil
That worked i picked the right start because there is apparently 2 of them in the text code -
S sdetweil has marked this topic as solved on
-
@sdetweil
Update for the Jan 1 2026,
This no longer fixes the issue. I used your update script and now i get this error;
sh: 1: ./node_modules/.bin.electron.js: not found -
@Sampleswow should not say electron.js
Do
cd ~/MagicMirror ls node_modules/electronIf not found do
npm install electron@39.2.7If successful
Donpm startPlease advise
-
@sdetweil
That fixed it for now. I guess will talk again next update lol, Thank you for your dedication to resolving my issue!
