MM won't start after upgrading to 2.29.0

[sdetweil]

@JohnGalt can you show me more of the output? after starting Application,
there is a dump of system data
like this

2024-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 

[sdetweil]

@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 here

then run my fixuppm2.sh script
(same place as my install script, near the bottom of the page

[JohnGalt]

@sdetweil – I can do that. Would you want it here or email?

[JohnGalt]

@sdetweil – I sent you an email with extended pm2 logs output.

[sdetweil]

@JohnGalt did you do this

https://forum.magicmirror.builders/topic/19089/mm-won-t-start-after-upgrading-to-2-29-0

[JohnGalt]

@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.

[sdetweil]

@JohnGalt the log show me the wayland/pm2 confusion

i opened a pm2 issue about this back in the early spring

[JohnGalt]

@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?

[sdetweil]

@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

[JohnGalt]

@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.

[sdetweil]

@JohnGalt ok, dont know how to fix that

[JohnGalt]

@sdetweil – OK, thanks for the effort!

[JohnGalt]

@sdetweil – I was able to search out a fix.

For the benefit of anyone else running Wayland and wanting or needing to switch back to x11, see: https://linuxconfig.org/how-to-use-x-instead-of-wayland-on-ubuntu-22-04 where you are asked to edit one line in a file, then reboot.

sudo nano /etc/gdm3/custom.conf

I will mark this as solved now.

[sdetweil]

@JohnGalt fabulous!!