My new MagicMirror will not start with Wayland?

[sdetweil]

@rkorell I can ‘fix’ MagicMirror.sh to detect wayland/labwc and use

npm  run start:wayland

and if not

npm run start

switching so it WORKS seems like it takes some drastic changes…(erase electron config)…

I don’t know what is in the electron config folder, so can’t tell if there is a way to know you switched since last run…

[rkorell]

@sdetweil As I wrote initially “npm run start:wayland” doesn’t work …
(despite wayland configured).
And the “stored” auto-start option npm run start:x11 DOES work - for whatever reason.

VNC was really sluggish on this, performance a nightmare so - see above marked as “solution” I switched back to x11 and all is working fine.

In the meantime I’ve also managed to get MMM-Pir to work by idenitfying and correcting two errors in Bugsounet’s code …

Warm regards,
Ralf

[sdetweil]

@rkorell great work!

[sdetweil]

@rkorell i am thinking of pushing a change to mm.sh to run with what is detected

this is for new installs, i wont change existing on update

updated, release on next rev

[rkorell]

@sdetweil said in My new MagicMirror will not start with Wayland?:

@rkorell great work!

Ohhh - this from you!
Makes me proud.
Thanks!

Ralf

[sdetweil]

@rkorell my updated mm.sh fails when trying wayland, some fontconfig problem
npm run start:wayland

apt upgrade /full-upgrade fail… oh so much fun…

but npm start works!?

[rkorell]

@sdetweil said in

but npm start works!?
Not tried.
Leave it currently, as is.
Via your install script provided autostart calls npm run start:x11 - which works fine.

Regards,
Ralf

[sdetweil]

@rkorell yeh, i put it back