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.

    force_s3tc_enable overridden by environment.

    Scheduled Pinned Locked Moved Solved Troubleshooting
    13 Posts 3 Posters 3.4k Views 3 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 Offline
      siddhartha
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • evroomE Offline
        evroom
        last edited by

        I get the warning too, but MM does start.
        There are several hits using google.
        Seems to be a Chromium and HTML syntax issue.

        MagicMirror version: 2.30.0
        Raspberry Pi 4 Model B Rev 1.5 (8 GB RAM)
        Raspbian GNU/Linux 12 (bookworm)

        Test environment:
        MagicMirror version: v2.30.0
        Raspberry Pi 3 Model B Plus Rev 1.3 (1 GB RAM)
        Raspbian GNU/Linux 12 (bookworm)

        1 Reply Last reply Reply Quote 0
        • S Offline
          siddhartha
          last edited by

          i get warning but my MM doesn’t start i have tried so many solutions. but still no effect. do you have any idea where should i look for those HTML or chromium files ?

          S 1 Reply Last reply Reply Quote 0
          • evroomE Offline
            evroom
            last edited by

            Sorry, no idea.
            You could disable all modules (disabled: true,) and then enable them one by one (disabled: false,) until the issue appears.

            But also run cd ~/MagicMirror; npm run config:check to be sure you do not have a config issue.
            Perhaps the ATTENTION is not related to the config.

            MagicMirror version: 2.30.0
            Raspberry Pi 4 Model B Rev 1.5 (8 GB RAM)
            Raspbian GNU/Linux 12 (bookworm)

            Test environment:
            MagicMirror version: v2.30.0
            Raspberry Pi 3 Model B Plus Rev 1.3 (1 GB RAM)
            Raspbian GNU/Linux 12 (bookworm)

            1 Reply Last reply Reply Quote 0
            • S Offline
              siddhartha
              last edited by

              Thanks i will try that and if solves that i will post it here :)

              there is one more issue npm lodash.update vulnerability. i don’t think so that those are connected to each other.

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

                Are u using chrome as the browser?
                This error has been reported there frequently.

                Search force_s3tc_enable in google

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • S Offline
                  siddhartha
                  last edited by

                  Chromium. yeah i have seen many reports on google about this chrome/chromium :(

                  I think must be issue with the GPU or else the syntax . i am looking into it but cant find anything :(

                  1 Reply Last reply Reply Quote 0
                  • S Offline
                    siddhartha
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • S Away
                      sdetweil @siddhartha
                      last edited by sdetweil

                      @siddhartha so, what does 'does not start ’ mean?

                      npm start
                      in the Magic Mirror folder gets the command prompt back? or not
                      screen goes black, or not

                      have you done

                      export DISPLAY=:0
                      npm start
                      

                      on my mm I also have to

                      npm --enable-transparent-visuals --disable-gpu start
                      

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

                      1 Reply Last reply Reply Quote 0
                      • S Offline
                        siddhartha
                        last edited by

                        After upgrading OS. i faced problem with display.
                        i fixed some problem with
                        npm audit fix --force.

                        Then i shifted to VNC
                        used DISPLAY=:1 and then the magicmirror started.
                        but now there ware two process running at time.

                        MagicMirror with DISPLAY=:0
                        MM with DISPLAY=:1

                        so using pm2 i deleted MagicMirror and gave reboot.
                        everything worked perfectly. so i changed back DISPLAY=:0 in MM.

                        and gave reboot again…

                        and problem solved. no black screen no error :)

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 1 / 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