Read the statement by Michael Teeuw here.
MM won't start after upgrading to 2.29.0
-
@JohnGalt can you show me more of the output? after starting Application,
there is a dump of system data
like this2024-10-29 17:55:20.819] [INFO] System information: ### SYSTEM: manufacturer: ; model: ; virtual: false ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.6.51+rpt-rpi-v8 ### VERSIONS: electron: 31.7.3; used node: 20.18.0; installed node: 20.9.0; npm: 10.1.0; pm2: 5.4.2 ### OTHER: timeZone: America/Chicago; ELECTRON_ENABLE_GPU: undefined -
@JohnGalt this is a pm2 problem…
SOMEtimes we can fix it like this
pm2 stop all pm2 delete MagicMirror pm2 save -f sudo npm remove pm2 -g # I edited a typo herethen run my fixuppm2.sh script
(same place as my install script, near the bottom of the page -
@sdetweil – I can do that. Would you want it here or email?
-
@sdetweil – I sent you an email with extended pm2 logs output.
-
-
S sdetweil referenced this topic on
-
@sdetweil – I wasn’t sure you [still] wanted me to do that before you had a chance to see the extended pm2 logs outputs. I will do it now and get back to you.
-
@JohnGalt the log show me the wayland/pm2 confusion
i opened a pm2 issue about this back in the early spring
-
@sdetweil – I did the pm2 work you asked for, and still have the same results.
As this is a dev instance it’s not as critical as it might be for the regular [production] instance we use to get actual information. Am I better off just re-installing Magic Mirror from scratch on this machine?
-
@JohnGalt its not MagicMirror its pm2 talking to the display manager
you could use raspi-config to set the display manager back to x11
without doing anything else
-
@sdetweil – Humm, I see what you mean. unfortunately this isn’t running on an actual Raspberry Pi so I don’t have that utility available to me.
It’s a VM running Ubuntu 23.10. If you can point me in the right direction, I’d be willing to give it a shot.
