Failed to Connect to Wayland Display

[sdetweil]

@atwist script name error, I made a shortcut for mm and didn’t catch it expanding there

[atwist]

@sdetweil ahh okay. I do have that file. What am I looking for in it though.?

[sdetweil]

@atwist can you run this from the command line , and show the results

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

[atwist]

nothing is returned

[sdetweil]

@atwist ok, weird, that is the command set I use on mm.sh to determine if Wayland is running or not

Does your mm.sh have those commands listed?

[atwist]

@sdetweil

Yes it does:

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc 
   # 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 start
fi

[sdetweil]

@atwist
So it shouldn’t be trying to start using wayland
And npm start on 2.34.0 uses x11

[atwist]

weird. Any suggestionon what to do?

[sdetweil]

@atwist move the script to another name
Try this instead

#!/bin/bash
npm start

Save that as mm.sh then do

chmod +x mm.sh

Then try
pm2 start MagicMirror

[atwist]

@sdetweil thanks. It shows that the process started successfully but it doesn’t appear on the screen.

[sdetweil]

@atwist you are on the pi directly, right? Not via ssh or vnc

[sdetweil]

@atwist try adding these two lines in front of the

export DISPLAY=:0
export ELECTRON_OZONE_PLATFORM_HINT=x11

npm start line

And try the
./MagicMirror.sh again.

May need to reboot before retry

[atwist]

@sdetweil yes directly on it