MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    My new MagicMirror will not start with Wayland?

    Scheduled Pinned Locked Moved Solved Troubleshooting
    17 Posts 2 Posters 803 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Away
      sdetweil @rkorell
      last edited by

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

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

      no idea

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 0
      • S Away
        sdetweil @rkorell
        last edited by

        @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…

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 0
        • S Away
          sdetweil @rkorell
          last edited by

          @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…

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          R 1 Reply Last reply Reply Quote 0
          • R rkorell has marked this topic as solved on
          • R Offline
            rkorell @sdetweil
            last edited by

            @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

            S 2 Replies Last reply Reply Quote 1
            • S Away
              sdetweil @rkorell
              last edited by

              @rkorell great work!

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              R 1 Reply Last reply Reply Quote 0
              • S Away
                sdetweil @rkorell
                last edited by 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

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                S 1 Reply Last reply Reply Quote 0
                • R Offline
                  rkorell @sdetweil
                  last edited by

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

                  @rkorell great work!

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

                  Ralf

                  1 Reply Last reply Reply Quote 0
                  • S Away
                    sdetweil @sdetweil
                    last edited by

                    @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!?

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    R 1 Reply Last reply Reply Quote 0
                    • R Offline
                      rkorell @sdetweil
                      last edited by

                      @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

                      S 1 Reply Last reply Reply Quote 0
                      • S Away
                        sdetweil @rkorell
                        last edited by

                        @rkorell yeh, i put it back

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy