Failed to Connect to Wayland Display

sdetweil

@atwist how does MM get started?

using pm2?

if so, find the startup command

pm2 status
pm2 info xxxx
where xxxx is the name or number on the row of the app you want info about

you need the value next to
script path

then examine that file…

atwist

Yes, pm2.

Here is that file.

#!/bin/bash

This file is still here to keep PM2 working on older installations.

cd ~/MagicMirror
DISPLAY=:0 npm start

sdetweil

@atwist yes, that is the file, should have started in default mode

there is an updated version

can you replace all the lines of text there with this

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

atwist

I updated that file but the error still exists.

0|MagicMirror | [3709:0102/125357.807528:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
0|MagicMirror | [3709:0102/125357.807690:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
0|MagicMirror | [3709:0102/125357.807720:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
0|MagicMirror | /home/twist/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

sdetweil

@atwist interesting

can you do this

cd ~/MagicMirror
npm start

atwist

Yes, that starts everything and gets me running like normal. Thanks!

So how do I get it to run on reboot moving forward?

sdetweil

@atwist weird… all the script does is the same thing…

can you show me the part of the output from npm start like from my desktop

####  System Information  ####
- SYSTEM:   manufacturer: System manufacturer; model: System Product Name; virtual: false; MM: 2.34.0
- OS:       platform: linux; distro: Ubuntu; release: 22.04.5 LTS; arch: x64; kernel: 5.15.0-164-generic
- VERSIONS: electron: undefined; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14
- ENV:      XDG_SESSION_TYPE: x11; MM_CONFIG_FILE: undefined
            WAYLAND_DISPLAY:  undefined; DISPLAY: :0.0; ELECTRON_ENABLE_GPU: undefined
- RAM:      total: 48077.13 MB; free: 36485.14 MB; used: 11591.98 MB
- OTHERS:   uptime: 21764 minutes; timeZone: America/Chicago

you may have to npm start >somefile.txt
then once up, ctrl-q,
and edit the somefile.txt

atwist

Here is that information.

System Information

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.5; virtual: false; MM: 2.34.0
OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.47+rpt-rpi-v8
VERSIONS: electron: 39.2.7; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14
ENV: XDG_SESSION_TYPE: x11; MM_CONFIG_FILE: undefined
WAYLAND_DISPLAY: undefined; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
RAM: total: 3796.86 MB; free: 2669.80 MB; used: 1127.06 MB
OTHERS: uptime: 3427 minutes; timeZone: America/Chicago

atwist

Do you happen to have any ideas to fix it moving forward? Thanks!

sdetweil

@atwist how are you starting MagicMirror?

pm2? How did you install MagicMirror

If my script, then look at
~/MagicMirror/installers/mm.sh

chrisfr1976

@atwist
You could try this as start script:


#!/bin/bash
cd ~/MagicMirror

export DISPLAY=:0
export ELECTRON_OZONE_PLATFORM_HINT=x11

npm start

The --ozone-platform-hint=x11 flag overrides the automatic detection and forces Electron into X11 mode. Maybe……

atwist

I don’t remember how i installed it but I don’t have MagicMirro.sh so i must not have used your script.

atwist

@chrisfr1976 Thanks for the reply. Sorry but how would i do that?

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