@sdetweil said:

@Scruffy I strongly recommend using some backup/restore mechanism,
please see my backup/restore scripts for one approach.

they also support versioning, so you can tell one set of changes from another and can go back or forward…
and move between systems. too…

https://github.com/sdetweil/MagicMirror-backup-restore.git

and I also support the install/upgrade scripts, mentioned in the MM doc, Alternative install section

OK perfect! I’ll run through this process next time this occurs. Thanks!

Do you see wayland_display in the list?

The script sets WAYLAND_DISPLAY if not already set

Here is the script , make sure to make it executable
chmod +x mm.sh

#!/bin/bash
cd ~/MagicMirror

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then 
   # if WAYLAND_DISPLAYis set, use it, else set to -0
   export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
   npm run start:wayland
else
   DISPLAY=:0 npm run start:x11
fi 

echo $XDG_SESSION_TYPE

returns nothing.

I am thinking of going the pm2 route and trying to launch using your aforementioned script but I can’t imagine it would yield another result.

We changed
npm start/node —run start

To launch for Wayland compositor

If you are still on x11
You need to use

npm run start:x11
Or
node —run start:x11

I followed all of the standard manual install steps, have git and node and npm.

This is what I am getting when attempting to run ‘node --run start’

Starting server on port 8080 …
[1877:0409/161415.143762:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[1877:0409/161415.143988:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[1877:0409/161415.144045:ERROR:ui/aura/env.cc:246] The platform failed to initialize. Exiting.
/home/onthewall/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

System Information

• SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.2; virtual: false; MM: v2.35.0
• OS: platform: linux; distro: Debian GNU/Linux; release: 13; arch: arm64; kernel: 6.12.75+rpt-rpi-v8
• VERSIONS: electron: 41.1.0; used node: 24.14.1; installed node: 24.14.1; npm: 11.11.0; pm2:
• ENV: XDG_SESSION_TYPE: undefined; MM_CONFIG_FILE: undefined
  WAYLAND_DISPLAY: wayland-1; DISPLAY: undefined; ELECTRON_ENABLE_GPU: undefined
• RAM: total: 3796.68 MB; free: 3304.59 MB; used: 492.10 MB
• OTHERS: uptime: 1 minutes; timeZone: America/Los_Angeles

they also support versioning, so you can tell one set of changes from another and can go back or forward…
and move between systems. too…

https://github.com/sdetweil/MagicMirror-backup-restore.git

and I also support the install/upgrade scripts, mentioned in the MM doc, Alternative install section

I copied over the old config.js which has all my module settings.

I installed MM from scratch along with all the modules. I then brought up both config.js files in Geany and copied and pasted over my configurations.

Not the cleanest of methods but it worked lol.

How did you migrate your config ?
Just interested in how people do things

I have MagicMirror back up and running using a new SD card. I’m guessing the old one died for whatever reason since the whole system was becoming extremely sluggish to the point it would take 10 seconds between input commands triggering.

Glad to be back up and running!

Thank you again for all your help troubleshooting and support us!

Cheers!

             total       used      free      shared     buff/cache   available
Mem:         3992        2153      210       550        2126         1839
Swap:        511         30        481

Is the output in MB? Doesn’t seem like it’s to the point where everything is so slow to respond.

leading to more swapping. This can affect performance because of the speed of the SD card.

free -m

will tell you how much memory and swap space you are using.

https://github.com/sdetweil/MagicMirror-backup-restore
Backup, copy off backup folder, tiny size

Install new MagicMirror and copy back folder and restore

@sdetweil said:

npm run start:wayland

Unfortunately, still no go.

The whole system is feeling sluggish… I wounder if it’s an SD issue…?

I have a new SD card arriving later today. I’ll image and reinstall MM and report back.

If it’s still not working, I’ll provide the logs again.

Cannot thank you enough, @sdetweil. You’re incredibly responsive and your support is greatly appreciated.

Cheers!

npm run start:wayland

I ran the first command and this is the output:

~ $ ps -ef | grep -v grep | grep -i -e xway -e labwc
ferguson   66504       1  0 15:32 ?        00:00:01 /usr/bin/Xwayland -auth /home/ferguson/.Xauthority :0 -rootless -core -terminate 10 -listenfd 28 -listenfd 29 -displayfd 88 -wm 82

When I run the last commands, it’s still not launching. The MM screen flickers up for a second and then goes away. This isn’t unique to the above steps.

Logs look similar, if not the same:

[306765:0406/201018.874374:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[306765:0406/201018.874626:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[306765:0406/201018.874711:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.
/home/ferguson/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[307094:0406/201032.033709:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[307094:0406/201032.033832:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[307094:0406/201032.033866:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.
/home/ferguson/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

Strange indeed.

ps -ef | grep -v grep | grep -i -e xway -e labwc

Then do

pm2 stop all
cd MagicMirror 
npm run start:x11

Does MagicMirror start now?

I’m having a similar issue and I’ve been following this post but I still can’t resolve the error.

[94483:0406/164800.222694:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[94483:0406/164800.222815:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[94483:0406/164800.222849:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.
/home/ferguson/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
[94821:0406/164812.960910:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[94821:0406/164812.962540:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[94821:0406/164812.962598:ERROR:ui/aura/env.cc:246] The platform failed to initialize.  Exiting.

I’m currently using the following lines in mm.sh

#!/bin/bash
cd ~/MagicMirror

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then
   # if WAYLAND_DISPLAYis set, use it, else set to -0
   export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
   npm run start:wayland
else
   npm run start:x11
fi

Running the PM2 shows the status is online.

Any help would be greatly appreciated.

Cheers!

Need some time to fix for existing

I have fixed upgrade to update mm.sh for start:x11 if wayland is not running

#!/bin/bash
cd ~/MagicMirror

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then
   # if WAYLAND_DISPLAYis set, use it, else set to -0
   export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
   npm run start:wayland
else
   npm run start:x11
fi