Failed to Connect to Wayland Display

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

atwist

@sdetweil the file you are referring to is in the installers folder. Correct?

It does start the interface with your suggestions. Is it able to start it in reboot since it no longer does?

sdetweil

@atwist

pm2 status
Then
pm2 start xxx

Where xxx is the name or number of the row in the status output

Then pm2 save

And the sudo reboot

atwist

@sdetweil Unfortunately, it still doesn’t start after reboot. It does continue to work if i start it manually.

Log file
|MagicMir | [2991:0228/201716.146315:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
0|MagicMir | [2991:0228/201716.146344:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
0|MagicMir | /home/twist/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
0|MagicMir | [3075:0228/201721.692197:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)

sdetweil

@atwist do this

pm2 status
pm2 info xxxx

where xxxx is the name/number on the row that contains the MagicMirror app

see the line in the output (example from my Mac, )

 script path       │ /Users/sam/MagicMirror/installers/mm.sh

is it pointing to the correct sh file??

hrt13

@atwist
I know this may be a bit late, I had the same problem on my Raspberry Pi3 after I updated to the latest MM.
I spent some time trying to get Wayland running, but wasn’t really successful. Finally, I changed my mm.sh script to:

#!/bin/bash
cd ~/MagicMirror

npm run start:x11

And that got it working again using: pm2 start|restart mm

sdetweil

@hrt13 yes, the release notes indicate that the npm start defaults to Wayland now…

VinGroot

@hrt13

@hrt13 said:

@atwist
I know this may be a bit late, I had the same problem on my Raspberry Pi3 after I updated to the latest MM.
I spent some time trying to get Wayland running, but wasn’t really successful. Finally, I changed my mm.sh script to:

#!/bin/bash
cd ~/MagicMirror

npm run start:x11

And that got it working again using: pm2 start|restart mm

I got something similar, my version of mm.sh:

#!/bin/bash
cd /home/pi/MagicMirror
DISPLAY=:0 node --run start:x11

hrt13

@sdetweil I modified your script from earlier to:

#!/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