Read the statement by Michael Teeuw here.
ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf:
-
@sdetweil I accidentally removed the post for npm start output and have been waiting for it to be re-posted, but it is still in the post queue. I have no idea what to do next? Should I re-install 32 OS instead and try to run the MagicMirror install script again or install an older MagicMirror version that used to work?
-
@ereborinkorppi I was waiting for you to respond… and u did… so I just rejected the post that was marked as spam. like my message should have said
-
@ereborinkorppi it would be interesting to see the 32 bit results…
-
@sdetweil I will give it a go if no easier solutions available, but will take some time before I can test it. Thank you so far, will report later what happened.
-
@ereborinkorppi i just don’t know… we are not using GPU, that error is related to GPU.
says happening in chromium, but we are not using chromium… so… at a loss.I see it on my pi3 in 32 bit mode, but it doesn’t stop mm…
-
@ereborinkorppi sorry I hit the reject button, can u resubmit.
-
@sdetweil
Hi I’m a nooby, I’m seeing the same errors in my startup but MM still runs OK. The only reason I found it was because I can’t get the MMM-OpenWeatherMapForecast to display just says loading?
I’m wondering now if the error has nothing to do with module running. -
@eyesallin do you see any errors from openweathermapforecast in the place you start mm
-
@sdetweil
Thx for responding, the only errors are[MMM-OpenWeatherMapForecast] 7-Jan-24 09:08 ** ERROR ** null
ERROR:gbm_wrapper.cc(253)] Failed to export buffer to dma_buf: No such file or directory (2)
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl (…/…/third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
at CreateVkInstance (…/…/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
at Initialize (…/…/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
at Create (…/…/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
at operator() (…/…/third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) -
@eyesallin said
[MMM-OpenWeatherMapForecast] 7-Jan-24 09:08 ** ERROR ** null
yeh not very useful, but there was an error
-
Thanks for information
-
@fethiyetours can u edit the module node_helper.js and change the error path like this
} else { /// this is the current line 62 if(response.statusCode != 200) console.log("[MMM-OpenWeatherMapForecast] " + moment().format("D-MMM-YY HH:mm") + " statusCode " + response.statusCode); else console.log("[MMM-OpenWeatherMapForecast] " + moment().format("D-MMM-YY HH:mm") + " ** ERROR ** " + error); }I’m guessing the statuscode will be 401, unauthorized
-
@sdetweil sorry for the delay. I guess I posted about my 32bit test. So I installed new 32 os and MagicMirror with the script, nothing extra, no own settings. Still gives me the same error message, and like for others here it doesn’t load the weather module (in sample config file) without any extra errors. If I switch to my own config (without any 3rd party modules) it doesn’t load all of my calendars (no other errors than the gbm_wrapper) and the whole MagicMirror gets stuck. Can’t even quit it without killing it.
-
@ereborinkorppi I see that error on my pi too, but it doesn’t interfere with operations.
would you be willing to to do a backup of your system using my backup/restore scripts
https://github.com/sdetweil/MagicMirror-backup-restore
and send me the three files. to my email,
sane userid as here at gmailconfig.js, custom.css and the module list
to email js files you have to rename to .txt
-
@sdetweil Wondering if there was a resolution here. I just did a brand new install on a Pi4b v1.5 using the script. I’ve not added any modules or changed the default config file in any way.
During the setup, I saw this (probably unrelated)
/usr/lib/aarch64-linux-gnu/plymouth/.so does not exist Splashscreen: Couldn't change theme to MagicMirror! don't know how to disable screen saver on labwc compositorI added the
export ELECTRON_DISABLE_GPU=1to the mm.sh
but had no effect.
I noticed this in the logELECTRON_ENABLE_GPU: undefined[39m .and tried adding
export ELECTRON_ENABLE_GPU =0but it had no effect except to change the “undefined” to “0”
-
we disabled GPU by default, to eliminate many errors, for most users
the plymouth message from my script is because the old way doesn’t work , but i dont know yet the right way
the error message from electron appears to be a bug, and we cant suppress it, sorry
-
@sdetweil No worries. Thanks for the response.
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