• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.

ERROR:gbm_wrapper.cc(253) Failed to export buffer to dma_buf: No such file or directory

Scheduled Pinned Locked Moved Solved Troubleshooting
15 Posts 3 Posters 7.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
    sdetweil @dathbe
    last edited by sdetweil Apr 16, 2025, 3:03 AM Apr 16, 2025, 3:01 AM

    @dathbe I tried to make it dynamically select, but that didn’t work, so its commented out
    ‘’’ is a bash block comment

    someone posted that npm run start:wayland worked for them to clear those errors…

    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 @dathbe
      last edited by sdetweil Apr 16, 2025, 3:07 AM Apr 16, 2025, 3:03 AM

      @dathbe said in ERROR:gbm_wrapper.cc(253) Failed to export buffer to dma_buf: No such file or directory:

      export ELECTRON_DISABLE_GPU=1

      the default now is disabled…

      and the env var has changed to
      export ELECTRON_ENABLE_GPU=1
      to turn it on

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      D 1 Reply Last reply Apr 16, 2025, 4:13 AM Reply Quote 0
      • D Offline
        dathbe @sdetweil
        last edited by dathbe Apr 16, 2025, 4:13 AM Apr 16, 2025, 4:13 AM

        @sdetweil
        No luck. with DISPLAY=:0 npm start, I get the long list of errors, but everything seems to work ok with the mirror. with

        WAYLAND_DISPLAY=wayland-1   
           npm run start:wayland
        

        It throws other errors and gets stuck in what seems to be a restart loop.

        0|mm  | [3351:0415/211257.942494:ERROR:wayland_connection.cc(199)] Failed to connect to Wayland display: No such file or directory (2)
        0|mm  | [3351:0415/211257.942729:ERROR:ozone_platform_wayland.cc(276)] Failed to initialize Wayland platform
        0|mm  | [3351:0415/211257.942774:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
        0|mm  | /home/mmuser/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
        
        S 1 Reply Last reply Apr 16, 2025, 4:19 AM Reply Quote 0
        • S Offline
          sdetweil @dathbe
          last edited by Apr 16, 2025, 4:19 AM

          @dathbe yeh, thats what I found too…
          maybe its labwc display now?

          from the labwc doc,
          https://labwc.github.io/labwc-config.5.html

          it sounds like DISPLAY is the correct variable

          The autostart file is executed as a shell script after labwc has read its configuration and set variables defined in the environment file. Additionally, the environment variables WAYLAND_DISPLAY and (when labwc is built with Xwayland support) DISPLAY will be defined
          

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          D 1 Reply Last reply Apr 16, 2025, 5:02 PM Reply Quote 0
          • D Offline
            dathbe @sdetweil
            last edited by dathbe Apr 16, 2025, 5:05 PM Apr 16, 2025, 5:02 PM

            @sdetweil

            I tried all three options in raspi-config > Advanced > Wayland (those being 1) X11, 2) Wayfire, and 3) Labwc), and was getting the same error on all of them. I went back to Labwc because my understanding is that is the current recommended.

            I’ve tried many different combinations. Anything having to do with start:wayland seems to truly fail and get stuck in a restart loop. npm run start:wayland technically works, but throws about 20 ugly error messages on start.

            Various options I’ve tried:

            # Work with error messages 
            DISPLAY=:0 npm start
            
            export ELECTRON_DISABLE_GPU=1
            DISPLAY=:0 npm start
            
            export ELECTRON_ENABLE_GPU=1
            DISPLAY=:0 npm start 
            
            # Cause endless start loop
            
            npm run start:wayland
            
            export ELECTRON_DISABLE_GPU=1
            npm run start:wayland
            
            export ELECTRON_ENABLE_GPU=1
            npm run start:wayland
            
            WAYLAND_DISPLAY=wayland-1
            npm run start:wayland
            
            DISPLAY=wayland-1
            npm run start:wayland
            
            S 1 Reply Last reply Apr 16, 2025, 5:24 PM Reply Quote 0
            • S Offline
              sdetweil @dathbe
              last edited by Apr 16, 2025, 5:24 PM

              @dathbe restart loop is pm2, its job is to keep the app running

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              D 1 Reply Last reply Apr 16, 2025, 7:00 PM Reply Quote 0
              • D Offline
                dathbe @sdetweil
                last edited by Apr 16, 2025, 7:00 PM

                @sdetweil Ok. When I have some time, I’m going to test an install with 32-bit PiOS.

                S 1 Reply Last reply Apr 16, 2025, 7:06 PM Reply Quote 0
                • S Offline
                  sdetweil @dathbe
                  last edited by Apr 16, 2025, 7:06 PM

                  @dathbe 32bit is x11 only . as i recall

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  D 1 Reply Last reply Apr 16, 2025, 11:02 PM Reply Quote 0
                  • D Offline
                    dathbe @sdetweil
                    last edited by Apr 16, 2025, 11:02 PM

                    @sdetweil It appears to load labwc by default, but either way it didn’t do anything different – fails to start with start:wayland and multiple phantom errors with start. I guess I just have to close my eyes and not read the logs on startup. Though weird it’s doing it with my Pi 4B, but not my Pi 2B.

                    S 1 Reply Last reply Apr 16, 2025, 11:32 PM Reply Quote 0
                    • S Offline
                      sdetweil @dathbe
                      last edited by Apr 16, 2025, 11:32 PM

                      @dathbe yeh some config setup, i think something in /boot/config. txt

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

                      D 1 Reply Last reply Apr 17, 2025, 10:10 PM Reply Quote 0
                      • 1
                      • 2
                      • 1 / 2
                      1 / 2
                      • First post
                        9/15
                        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