@sdetweil Good evening, I tried npm start, npm run start:wayland --disable-gpu, node --run start, and a variety of other variations that I ran across while troubleshooting. I did read through your install script to see if there was something in there I may be able to try. I didn’t see anything that helped point me to how to correct the issue.

I’ve been using MM2 for a long time and I know that you’ve provided lots of great support so decided to rename my MagicMirror folder, run your raspberry.sh installer and see if that would get it working.

Good news, it is working [HUGE THANK YOU]! Bad news, I’m not sure what fixed it.

Since I started with a vanilla install from the official docs I’ll probably start over in a couple days to see if I can recreate the issue. I’ll report back if I find out what the issue was and what fixed it in case it may help someone else, but now that I know it will run on my RPi 3b with Trixie running Wayland I don’t want to take up any more of your or the other devs time on.

I truly appreciate what you do for this project and the help you provide on this forum!

-Cheers

@sdetweil Good evening, I tried npm start, npm run start:wayland --disable-gpu, node --run start, and a variety of other variations that I ran across while troubleshooting. I did read through your install script to see if there was something in there I may be able to try. I didn’t see anything that helped point me to how to correct the issue.

I’ve been using MM2 for a long time and I know that you’ve provided lots of great support so decided to rename my MagicMirror folder, run your raspberry.sh installer and see if that would get it working.

Good news, it is working [HUGE THANK YOU]! Bad news, I’m not sure what fixed it.

Since I started with a vanilla install from the official docs I’ll probably start over in a couple days to see if I can recreate the issue. I’ll report back if I find out what the issue was and what fixed it in case it may help someone else, but now that I know it will run on my RPi 3b with Trixie running Wayland I don’t want to take up any more of your or the other devs time on.

I truly appreciate what you do for this project and the help you provide on this forum!

-Cheers

@rkorell So… Glad to hear you got it working with Wayland. I attempted to upgrade from Bookworm to Trixie (RPi 3b running Raspbian) and torked my system. I decided to reinstall fresh and have a fully working Trixie with Wayland. I’ve upgaded to latest for both Node.js and NPM. Unfortunately, I still can’t get MagicMirror to start. This is where I’m at:
[7904:0415/203748.805365:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[7904:0415/203748.806445:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[7904:0415/203748.806688:ERROR:ui/aura/env.cc:246] The platform failed to initialize. Exiting.
/home/josh/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

I’ve run through a bunch of different start up options for the display from the forum but just can’t seem to make electron happy.

Any thoughts would be appreciated.