Electron Error

nobbie35

@sdetweil I agree with its a node problem.

~/Dashboard/MagicMirror $ which node
/home/pi/.nvm/versions/node/v24.16.0/bin/node

sdetweil

@nobbie35 ok, you are using nvm

nvm install 22.22.1
nvm use 22.22.1
hash -r
node -v

if 22.22.1

cd ~/MagicMirror
rm -rf node_modules
npm run install-mm

if successful

npm run start:wayland

advise results

nobbie35

Ok this fixed this issues… I’m not using wayland its still x11 i know that… I just have to go update my config file and main.css to match what I had in my previous implementation.

Thank you for the assist. Much appreciated

sdetweil

@nobbie35 said: node 22, awesome
hmmm this says wayland

 ps -ef | grep -v grep | grep -i -e xway -e labwc

can you show its output

note we moved (user controlled files) like css to the config folder
IF you used my installer script, it would have moved everything other than the MM owned css contents

please don’t edit main.css

all USER css goes in custom.css
that way when we install updates, we dont overwrite your stuff…

nobbie35

I noticed that nothing seems to be working from my config on this new version. I was running 2.25 and all of my custom config was in the main.css. I decided to format another microsd card with a backup of my old MagicMirro and I’m planning on installing that. I’m sure that i’ll run into a node/electron issue running the older version. I’m debating just starting from scratch with the new version and wrestling with google and microsoft authentications…

sdetweil

@nobbie35 main.css is ours, we will write over it every release. All user css goes in custom.css
Now located in the config folder

If you used my backup restore it can help you move versions and systems, backup here restore there

My installer creates custom.css if it doesn’t exist
My updater would have moved things around for you

sdetweil

@nobbie35 if you have an older system, even if it’s not running completely you can use my backup/restore
Install new MagicMirror w my script
Run restore to put back modules , config and css if it was in custom.css

Best thing to do for things in main.css

Do a git diff main.css

It will show you all the changes and adds

nobbie35

unfortunately I don’t have a running system. the microsd card failed and I had the raspi rainbow screen. I have the MagicMirror folder copied to my NAS. Not sure if that would help with your tool or not.
At this point I’m considering just starting from scratch adding my modules and then get it all up and running. I have my config.js and the main.css that I modified. If thats all i need let me know and where your script is and Ill go to work. I did make a fork of 2.25 and made changes to magic mirror myself to suit my needs which I don’t plan on doing.

sdetweil

@nobbie35 scripts are here, mentioned in MagicMirror install doc
https://github.com/sdetweil/MagicMirror_scripts

Backup/restore should work if you can run it from the nas command line (it’s all bash) and if git is there you could push to a repo of yours

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

This takes optional parm’s for the folder name of MagicMirror and the place to put the backup

FrostByte

I am using

~/MagicMirror$ node -v
v26.3.0

and

"optionalDependencies": {
	"electron": "^42.3.2"
},
"overrides": {
	"yauzl": "^3.3.1"
}

within ~/MagicMirror/package.json
and it is working.

sdetweil

@FrostByte cool…

we try to stay in sync with electron, because there is a scenario for some modules, where

mm running
npm run server generates one binary version, need node rebuild to match current node binary
and
npm run start:…
requires a different binary , fixed with electron rebuild (which we don’t ship, but I add in the scripted install

AND when the module ships from the author, it may have a DIFFERENT binary than BOTH those choices…
(SOOOOO much fun)

anyhow, we have tried to keep from having that problem rear is head all the time…

also, starting with node 24, there are no more 32 bit nodejs pre-compiled binaries… which means it won’t run on older 32 bit (smaller memory footprint) systems…