• 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 6.9k 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.
  • R Offline
    rrslssr
    last edited by Nov 13, 2023, 5:47 PM

    This would seem to be a minor irritation rather than an issue, but…
    My system was installed using @sdetweil’s installation script.
    MM seems to be working and displaying properly on my system:

    • Linux magicmirror 6.1.0-rpi6-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27) aarch64 GNU/Linux
    • /bin/bash: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=198ac6b0cc01bf774c5746a36a6fd31dead9bda5, for GNU/Linux 3.7.0, stripped

    However, I get these errors are displayed quickly after starting MM:

    …
    [13.11.2023 12:28.38.427] [LOG] Launching application.
    [6982:1113/122839.369692:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.371506:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.372947:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.374394:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.375867:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.377332:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.378891:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.382146:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.383645:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.385641:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.388818:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.390166:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.392742:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
    [6982:1113/122839.395676:ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)

    Are these errors something I should worry about and correct, or can I just ignore them?

    Thanks.

    S 1 Reply Last reply Nov 13, 2023, 5:51 PM Reply Quote 0
    • R Offline
      rrslssr
      last edited by Nov 13, 2023, 6:16 PM

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

      export ELECTRON_DISABLE_GPU=1

      @sdetweil That did not work for those errors, but it did eliminate other errors further down.
      I’ll just ignore these.
      Thanks

      1 Reply Last reply Reply Quote 1
      • S Offline
        sdetweil @rrslssr
        last edited by Nov 13, 2023, 5:51 PM

        @rrslssr you can ignore them,

        OR add

        export ELECTRON_DISABLE_GPU=1
        

        before the npm start line in

        ~/MagicMirror/installers/mm.sh
        

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        D 1 Reply Last reply 29 days ago Reply Quote 0
        • R Offline
          rrslssr
          last edited by Nov 13, 2023, 6:16 PM

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

          export ELECTRON_DISABLE_GPU=1

          @sdetweil That did not work for those errors, but it did eliminate other errors further down.
          I’ll just ignore these.
          Thanks

          1 Reply Last reply Reply Quote 1
          • E ereborinkorppi referenced this topic on Jan 6, 2024, 3:16 PM
          • D Offline
            dathbe @sdetweil
            last edited by dathbe 29 days ago 29 days ago

            @sdetweil

            Is this still the right way to address these errors? This is what my ~/MagicMirror/installers/mm.sh file looks like:

            #!/bin/bash
            cd /home/mmuser/MagicMirror
            '''
            if [ $(ps -ef | grep -v grep | grep -e wayfire -e labwc | wc -l) -ne 0 ]; then 
               WAYLAND_DISPLAY=wayland-1   
               export ELECTRON_DISABLE_GPU=1
               npm run start:wayland
            else
               export ELECTRON_DISABLE_GPU=1
               DISPLAY=:0 npm start
            fi 
            '''
            export ELECTRON_DISABLE_GPU=1
            DISPLAY=:0 npm start  
            

            And I’m still getting the following errors:

            0|mm  | [2154:0415/185345.685943:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.686603:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.689774:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.690194:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.690550:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.690714:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.690957:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.691151:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.692895:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.693152:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.693449:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.693628:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.693878:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.694076:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.694390:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.694612:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.696528:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.696838:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.697254:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.697494:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.697824:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.698209:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.698617:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.698851:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.699185:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.699426:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.699753:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.700002:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.700357:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.700604:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            0|mm  | [2154:0415/185345.701001:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
            0|mm  | [2154:0415/185345.701225:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: No such file or directory (2)
            
            S 2 Replies Last reply 29 days ago Reply Quote 0
            • S Offline
              sdetweil @dathbe
              last edited by sdetweil 29 days ago 29 days ago

              @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 29 days ago 29 days ago

                @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 29 days ago Reply Quote 0
                • D Offline
                  dathbe @sdetweil
                  last edited by dathbe 29 days ago 29 days ago

                  @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 29 days ago Reply Quote 0
                  • S Offline
                    sdetweil @dathbe
                    last edited by 29 days ago

                    @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 29 days ago Reply Quote 0
                    • D Offline
                      dathbe @sdetweil
                      last edited by dathbe 29 days ago 29 days ago

                      @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 29 days ago Reply Quote 0
                      • S Offline
                        sdetweil @dathbe
                        last edited by 29 days ago

                        @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 29 days ago 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