Read the statement by Michael Teeuw here.
ERROR:gbm_wrapper.cc(253) Failed to export buffer to dma_buf: No such file or directory
-
Is this still the right way to address these errors? This is what my
~/MagicMirror/installers/mm.shfile 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 startAnd 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) -
@dathbe I tried to make it dynamically select, but that didn’t work, so its commented out
‘’’ is a bash block commentsomeone posted that npm run start:wayland worked for them to clear those errors…
-
@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 -
@sdetweil
No luck. withDISPLAY=:0 npm start, I get the long list of errors, but everything seems to work ok with the mirror. withWAYLAND_DISPLAY=wayland-1 npm run start:waylandIt 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 -
@dathbe yeh, thats what I found too…
maybe its labwc display now?from the labwc doc,
https://labwc.github.io/labwc-config.5.htmlit 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 -
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:waylandseems to truly fail and get stuck in a restart loop.npm run start:waylandtechnically 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 -
@dathbe restart loop is pm2, its job is to keep the app running
-
@sdetweil Ok. When I have some time, I’m going to test an install with 32-bit PiOS.
-
@dathbe 32bit is x11 only . as i recall
-
@sdetweil It appears to load labwc by default, but either way it didn’t do anything different – fails to start with
start:waylandand multiple phantom errors withstart. 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.
