Black screen after MM v2.4.0 update.

grantc66

Not sure if I’m having the same issue, stupidly updated electron as npm was claiming 1.7.13 had a critical vulnerability (after installing MMM-voice) Then got the backscreen issue. rolled back electron to 1.7.13 & the issue persists.

Node v9.11.1
npm 6.1.0

Thought I’d uploaded the log file but not sure if others can see it. That snippet below is the first error after ALL_MODULES_STARTED

13:01:19.440 main.js:40 Uncaught TypeError: Cannot read property ‘appendChild’ of undefined
at main.js:40
at Array.forEach ()
at createDomObjects (main.js:24)
at Object.modulesStarted (main.js:471)
at startModules (loader.js:59)
at loader.js:40
at HTMLLinkElement.stylesheet.onload (loader.js:203)
(anonymous) @ main.js:40
createDomObjects @ main.js:24
modulesStarted @ main.js:471
startModules @ loader.js:59
(anonymous) @ loader.js:40
stylesheet.onload @ loader.js:203

13:01:20.056 TypeError: Cannot read property ‘getElementsByClassName’ of null
at moduleNeedsUpdate (main.js:176)
at main.js:144
at Promise ()
at updateDomWithContent (main.js:137)
at main.js:119
at
Promise rejected (async)
(anonymous) @ main.js:121
Promise resolved (async)
(anonymous) @ main.js:118
updateDom @ main.js:109
updateDom @ main.js:514
updateDom @ module.js:358

Any pointers as to how to get it working again? It was working perfectly before MMM-voice & buggering around with electron.
Tried a fresh install with the same result :(

shane1234

I’m also having the black screen of death. I tried both overlay options, and I tried commenting it out alltogether. I also ran the 2.4.1 update, but still getting black screen. Runs normally with the new update though when I comment out the PIR module in the config.js file.

sdetweil

@shane1234 if u have the PIR module loaded, and do ctrl-shift-i (lower case letter i), it will open the debug env, and then select the console tab… do you see any errors?

also, if u start from a terminal window, alt-spacebar, n will minimze the mirror screen so you can see the terminal window node_helper outputs… anything there?

usually a module.js error kills with MM screen…

Sun

Mine after upgrade it’s freezing when trying to run magicmirror. Also try both kms driver and fake kms driver.

Dom1n1c

mine is also freezing after the update.
No difference if i connect via vnc or using the monitor.

The only thing that does work, is opening the mirror in another browser (http://magicmirror:8080)

Kimzer

Is there a different way to turn the screen on/off with the fake kms driver maybe? :s

Kimzer

@kimzer replying to myself. I just had to chmod the new pir script i made to make it work duhhh. :p

bwente

@joela85
Are you using MMM-PIR-Sensor?
https://github.com/paviro/MMM-PIR-Sensor/issues/49

I needed to delete the node_modules directory first. Then I ran npm install and the issue was gone.

joela85

@bwente
I’m not currently using MMM-PIR-Sensor.
My problem was Enabling the Open GL driver. Using “dtoverlay=vc4-kms-v3d” or “dtoverlay=vc4-fkms-v3d” did not work. Remove the line and it was fine. (Temps seem reasonable 62deg)

"Enable the Open GL driver to decrease Electron’s CPU usage.
The latest versions of electron use an extreme amount of CPU power when no Open GL driver is loaded. This will result in an overheating Raspberry Pi. To solve this issue, use the experimental desktop Open GL driver by adding the following line to /boot/config.txt:

sudo nano /boot/config.txt
Add the following line:

dtoverlay=vc4-kms-v3d
ℹ️ Activating the Open GL drive can also be accomplished by using the raspi-config tool by running sudo raspi-config. Go to the Advanced Options menu and select A7 GL Driver. Next, select the G1 GL (Full KMS) OpenGL desktop driver with full KMS. Note that this option will be selected in the menu even when the GL drive is not yet configured."

Not sure what the issue is. But at least it works.

shane1234

Ok, I cheated a little bit and completly wiped my SD card. Reinstalled Raspian, Magic Mirror and everything else from scratch, working great now!