Black screen with cursor issue.

[sdetweil]

@nx3xo in the script that does npm start
add

export ELECTRON_DISABLE_GPU=1

before the npm start line

with my install script, that is

~/MagicMirror/installers/mm.sh

[nx3xo]

@sdetweil

So one of my installs is mm.sh and the other is run-start.sh.

The mm.sh one only shows this error in start.

[2883:1218/201556.298300:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files

I think this has been covered and is insignificant, correct?

The run-start.sh one I’m going to reinstall.

Not sure how I ended up with 2 different installs, pretty I used your script.

So heres a question for ease of troubleshooting.

What if I do a couple dedicated proxmox lxc for servers and run the raspi displays as clients? I haven’t tried this method yet.

[nx3xo]

@sdetweil

Made change. No dice on my original MM device 4x4 pixelsquare. Black screen plus cursor. Startup out looks clean.

[sdetweil]

@nx3xo run-start is done when I cannot find electron or it’s armv6l

then I just launch chromium over the mm server

[nx3xo]

@sdetweil

I would like to sort this self hosted mm instance. It runs perfect in the web browser. Just blank screen with cursor. Is it possible a module can prevent everything from launching if it is too large and overlaps others?

[sdetweil]

@nx3xo how about the browser on the host looking at http://localhost:mm_port