My new MagicMirror will not start with Wayland?

[rkorell]

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

note that npm start issues npm run start:x11

? can you kindly please eloborate?
Didn’t get you, sorry!

[rkorell]

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

rm -rf ~/.config/Electron

quick question: will this command help, anyway to get “performance” fixed?
Background: Since running on Pi5 / bookworm the mirror has “problems” on reboot.
Module load is extremely slow (minutes!).
A “pm2 reload MagicMirror” after reboot leads to way faster module loadings.

Thanks,
Ralf

[sdetweil]

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

quick question: will this command help, anyway to get “performance” fixed?

no idea

[sdetweil]

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

Didn’t get you, sorry!

from package.json
these are the command types you can issue npm run …

                "start": "npm run start:x11",
                "start:dev": "npm run start -- dev",
                "start:wayland": "WAYLAND_DISPLAY=\"${WAYLAND_DISPLAY:=wayland-1}\" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland",
                "start:wayland:dev": "npm run start:wayland -- dev",
                "start:windows": ".\\node_modules\\.bin\\electron js\\electron.js",
                "start:windows:dev": "npm run start:windows -- dev",
                "start:x11": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js",
                "start:x11:dev": "npm run start -- dev",

if you do npm start or npm run start
the command is “npm run start:x11”

which is the “same” as it was before release 2.30.0

I posted this in
https://forum.magicmirror.builders/topic/19269/new-magicmirror-start-options-in-version-2-30-0

so at least you don’t have to edit package.json and break updates…

[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