@eightbit ok…

cd ~/MagicMirror
npm install electron@26.2.4

and try again, manually w
npm start

@eightbit can u show me the “start”: from package.json

@eightbit

delete one of them and replace the other with

		"start": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js",

also do uname -a

@eightbit you didn’t need to delete all the rest of the scripts

@danningson you should see messages where you start MM

I STRONGLY suggest NOT using pm2 during modules dev and testing
pm2 stop all

cd ~/MagicMirror
npm start >somefile.txt 2>&1

then all the messages will be in somefile.txt

ctrl-c in terminal window or ctrl-q on MM web page to stop

here is a message in the node_helper that should be triggered
console.log(‘[’ + self.name + '] ’ + ‘Users ’ + message.login.names.join(’ - ‘) + ’ logged in.’);

there is also a camera frame event but no logging, you could add a message there

all the CV work is done in python in the background, and its outputs messages to the handlers in node_helper

@MajorC download the update to MMM-DWD-WarnWeather

cd ~/MagicMirror/modules/MMM-DWD-WarnWeather
git pull
npm install

then restart magic mirror

@neastman You must start with a full version of the OS that has the graphical desktop.
MagicMirror uses a browser to display and all browsers display only in graphics mode

if you had used my automated script it would have aborted warning you of text mode

@rama3124 from the desktop, menu, upper left,
preferences, raspi configuration, screen, rotate

@Kelemvor no they are system config caused errors

you can turn off use of the GPU so you won’t get them anymore

in the script that you use to start mm, add

export ELECTRON_DISABLE_GPU=1

if you use my install script and use pm2 to autostart, that script is

~/MagicMirror/installers/mm.sh

in the next release, next week, we will disable GPU by default, and add a new env variable to enable it

export ELECTRON_ENABLE_GPU=1

@Benalze

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