Read the statement by Michael Teeuw here.
Failed to Connect to Wayland Display
-
@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 -
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 -
-
Yes, that starts everything and gets me running like normal. Thanks!
So how do I get it to run on reboot moving forward?
-
@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/Chicagoyou may have to npm start >somefile.txt
then once up, ctrl-q,
and edit the somefile.txt
