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.

    The `punycode` module is deprecated message after Upgrade from 2.33.0 to 2.35.0

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    13 Posts 2 Posters 43 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.
    • W Offline
      wmx
      last edited by

      After doing some more research I also updated my 3 additional modules manually.
      I thought the update script would also have done this , but it seems it didn’t. The module MMM-homeassistant-sensors wasn’t up to date.

      Now it ends with this message

      [2026-04-21 22:26:11.173] [LOG]   [app] Starting MagicMirror: v2.35.0
      [2026-04-21 22:26:11.199] [LOG]   [utils] Loading config ...
      [2026-04-21 22:26:11.212] [INFO]  [utils] Checking config file /home/somename/MagicMirror/config/config.js ...
      [2026-04-21 22:26:11.444] [INFO]  [utils] Your configuration file doesn't contain syntax errors :)
      [2026-04-21 22:26:11.446] [INFO]  [utils] Checking modules structure configuration ...
      [2026-04-21 22:26:11.643] [INFO]  [utils] Your modules structure configuration doesn't contain errors :)
      [2026-04-21 22:26:12.799] [LOG]   [MMM-homeassistant-sensors] MMM-homeassistant-sensors helper started...
      [2026-04-21 22:26:12.801] [LOG]   [MMM-MQTT] MMM-MQTT: Starting node helper
      [2026-04-21 22:26:13.859] [INFO]  [systeminformation]
      ####  System Information  ####
      - SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.2; virtual: false; MM: v2.35.0
      - OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.75+rpt-rpi-v8
      - VERSIONS: electron: 41.1.0; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14
      - ENV:      XDG_SESSION_TYPE: tty; MM_CONFIG_FILE: undefined
                  WAYLAND_DISPLAY:  wayland-1; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
      - RAM:      total: 3795.80 MB; free: 3025.94 MB; used: 769.87 MB
      - OTHERS:   uptime: 75 minutes; timeZone: Europe/Berlin
      /home/somename/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP
      

      My mm.sh contains

      cd ./MagicMirror
      export ELECTRON_DISABLE_GPU=1
      export NODE_EXTRA_CA_CERTS=/home/somename/.step/certs/root_ca.crt
      DISPLAY=:0 npm start
      

      Is there something else missing?

      S 2 Replies Last reply Reply Quote 0
      • S Offline
        sdetweil @wmx
        last edited by

        @wmx no. The modules are down level in their package.json dependencies.

        Sam

        How to add modules

        learning how to use browser developers window for css changes

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

          @wmx the upgrade script only upgrades the base, and does npm
          Install for the modules that have dependencies in their package.json.

          Upgrading modules is up to the author, and user for the process. Many times deprecated libraries force code changes on update.

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • W Offline
            wmx
            last edited by

            @sdetweil ok, understood.
            I updated my 3 additional modules but still get

            ~/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP
            

            If i switch to

            DISPLAY=:0 npm run server
            

            it starts and I can see the webpage in a browser, but no screen on my mirror. Here only the graphical desktop.
            What else can I do or check?

            S 2 Replies Last reply Reply Quote 0
            • S Offline
              sdetweil @wmx
              last edited by

              @wmx remember that npm start now does Wayland (from the release notes)
              So you have to change it to
              npm run start:x11
              If still using x

              If you used my upgrade script it should have fixed mm.sh if you used pm2 for launch

              Sam

              How to add modules

              learning how to use browser developers window for css changes

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

                @wmx just reinstalling the old module definition will not fix the old dependency. The author must change the module package

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • W Offline
                  wmx
                  last edited by

                  @sdetweil I used your scripts.
                  After Upgrade I switched to wayfire in raspi-config and rebooted.
                  But I can try to get back to X11 and try the additional parameter (:x11).
                  Two of the modules had updates. I updated these (git pull && npm install).

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

                    @wmx doesn’t sound like system was changed to Wayland. Did you reboot after changing in raspicfg

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    1 Reply Last reply Reply Quote 0
                    • W Offline
                      wmx
                      last edited by

                      yes, I did

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

                        @wmx
                        Can you run this command string

                        If Wayland it will output something

                        ps -ef | grep -v grep | grep -i -e xway -e labwc

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

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

                          Also can you try

                          export WAYLAND_DISPLAY=wayland-0
                          npm start
                          

                          Sam

                          How to add modules

                          learning how to use browser developers window for css changes

                          1 Reply Last reply Reply Quote 0
                          • W Offline
                            wmx
                            last edited by

                            @sdetweil
                            I switched back to X11 in raspi-config, rebooted and added the parameter

                            DISPLAY=:0 npm run start:x11
                            

                            That works! :-)
                            As it is quite after midnight here, I’ll do these tests with wayland tomorrow and respond here.
                            So far, thank you a lot.

                            1 Reply Last reply Reply Quote 1

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            • 1 / 1
                            • 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