Wayland question

[gonzonia]

I know this has been fixed (at least I think it has) I just can’t find what the fix is. My SD got corrupted so I’m re-installing. Clean install of PiOS on a Pi4b. Used @sdetweil script to install.

Starting with npm run start:wayland seems to work but when I reboot and it tries to start it doesn’t work.

What do I need to change?

[sdetweil]

@gonzonia no. I use ssh all the time, never real keyboard

The start:Wayland says

If WAYLAND_DISPLAY is set, use it, else set it to wayland-1
But
Maybe it needs to be wayland-0

So add
export WAYLAND_DISPLAY=wayland-0
Before the npm run start:Wayland line

And try that

[sdetweil]

@gonzonia MagicMirror/installers/mm.sh

But the latest should handle that

Where you do
npm run
Now

Do env
And look for WAYLAND_DISPLAY

What is its value?

[gonzonia]

@sdetweil

WAYLAND_DISPLAY=wayland-0

[gonzonia]

@sdetweil said in Wayland question:

MagicMirror/installers/mm.sh

I have a theory…I did the install via ssh and not directly on the pi. Maybe that broke it?

[sdetweil]

@gonzonia no. I use ssh all the time, never real keyboard

The start:Wayland says

If WAYLAND_DISPLAY is set, use it, else set it to wayland-1
But
Maybe it needs to be wayland-0

So add
export WAYLAND_DISPLAY=wayland-0
Before the npm run start:Wayland line

And try that

[gonzonia]

@sdetweil I think that worked. I was able to start it with pm2.

[sdetweil]

@gonzonia cool

[sdetweil]

I’ll see if I can mod the script, not til Monday

[schlomm]

Hi @sdetweil
I have tested your updated script and it works flawlessly. Exporting the needed WAYLAND environment variable was exactly what I was looking for.

Since I install MagicMirror via an Ansible playbook, the required environment variables are not set in the used .pm2/dump.pm2 file - my previous approach was to restore a prepared dump.pm2 file, but with your approach it is much more convenient :)

[sdetweil]

@schlomm awesome, thanks for the feedback