@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.

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

@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

@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

@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)

Is there any functional difference between MMM-Pages and MMM-Carousel? I’m using Carousel, but just stumbled across Pages and am wondering if the grass is greener on that side…

@BKeyport Awesome. Unrelated, but I love your MMM-Multimonth.

@sdetweil I’d rather have late and working consistently than early and missed because of lag. I suspect most people boot their mirror at most once a day, so waiting an extra 30 seconds for the module to show content doesn’t seem like that big of a deal.

But I’ll try DOM_OBJECTS_CREATED.

@mumblebaj No problem. I had the same problem on my repositories until I realized that I have to actively sign up for alerts. You can do that by clicking on the “Watch” icon at the top of the repository page, and then clicking either “All Activity” or “Custom” (and then selecting “Issues” and Pull Requests").

I’ve submitted a PR.

I will also submit a couple others to fix some console errors and get rid of the node-fetch dependency, though those issues are not breaking, so less important.

i was having trouble with a module reliably starting (might be my underpowered RasPi), and i thought maybe it was trying to load before the system was ready. so i moved some startup code from the start() function to a custom function that gets called after the module receives its MODULE_DOM_CREATED notification.

is this a bad idea, just useless, or might it actually do some good?