MMM-CalendarExt3 and MMM-MonthlyCalendar blank

[Scott-M]

Just to pick back up on this, I checked my bash history and I did npm run install-mm after the clipping fix.

I have tried a few times now to do this with the same result, this time without the clipping fix.

Reflashed the image and then the following steps are my bash history from first run of the OS. Only change to the config file is changing the port and the full whitelist. I selected No to the pm2 question, the screensaver was not disabled, just a waring about not knowing how to disable on an labwc compositor.

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"
cd ~/MagicMirror/config
nano config.js
npm run start

With the following results, MagicMirror doesn’t start. and doesn’t get any futher that the whitelist warning. Same result without the full whitlist though…

scott@MagicMirror:~/MagicMirror/config $ npm run start

> magicmirror@2.30.0 start
> npm run start:x11


> magicmirror@2.30.0 start:x11
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

[2025-03-25 09:38:22.852] [LOG]   Starting MagicMirror: v2.30.0
[2025-03-25 09:38:22.861] [LOG]   Loading config ...
[2025-03-25 09:38:22.862] [LOG]   config template file not exists, no envsubst
[2025-03-25 09:38:23.052] [INFO]  Checking config file /home/scott/MagicMirror/config/config.js ...
[2025-03-25 09:38:23.078] [INFO]  Your configuration file doesn't contain syntax errors :)
[2025-03-25 09:38:23.078] [INFO]  Checking modules structure configuration ...
[2025-03-25 09:38:23.117] [INFO]  Your modules structure configuration doesn't contain errors :)
[2025-03-25 09:38:23.119] [LOG]   Loading module helpers ...
[2025-03-25 09:38:23.119] [LOG]   No helper found for module: alert.
[2025-03-25 09:38:23.122] [LOG]   Initializing new module helper ...
[2025-03-25 09:38:23.122] [LOG]   Module helper loaded: updatenotification
[2025-03-25 09:38:23.122] [LOG]   No helper found for module: clock.
[2025-03-25 09:38:23.169] [LOG]   Initializing new module helper ...
[2025-03-25 09:38:23.169] [LOG]   Module helper loaded: calendar
[2025-03-25 09:38:23.170] [LOG]   No helper found for module: compliments.
[2025-03-25 09:38:23.170] [LOG]   No helper found for module: weather.
[2025-03-25 09:38:23.208] [LOG]   Initializing new module helper ...
[2025-03-25 09:38:23.208] [LOG]   Module helper loaded: newsfeed
[2025-03-25 09:38:23.208] [LOG]   All module helpers loaded.
[2025-03-25 09:38:23.211] [LOG]   Starting server on port 8089 ...
[2025-03-25 09:38:23.216] [WARN]  You're using a full whitelist configuration to allow for all IPs

Would be useful is someone can replicate this and see if it is something peculiar to my enviroment.

Raspberry Pi5 with 64 Bit Debian Bookworm with desktop.

I am just about to try with the 32 bit image but the whole process takes a while.

Update: couldn’t get it to install on the 32 bit version. New install of 32 bit bookworm, ran the install script and it fails with:

installing correct version of node and npm, please wait
/usr/local/bin/n: line 753: /usr/local/bin/node: cannot execute: required file not found
bash: line 309: /usr/local/bin/node: cannot execute: required file not found
node failed to install, exiting

[sdetweil]

@Scott-M i will examine and fix the installer

32bit on pi5 might never run as there were conflicting hardware changes

can you try to start for wayland?

npm run start:wayland

see https://forum.magicmirror.builders/topic/19269/new-magicmirror-start-options-in-version-2-30-0

[Scott-M]

@sdetweil said in MMM-CalendarExt3 and MMM-MonthlyCalendar blank:

npm run start:wayland

> magicmirror@2.30.0 start:wayland
> WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland

did not find extension DRI_Mesa version 1
failed to bind extensions
did not find extension DRI_Mesa version 1
failed to bind extensions
did not find extension DRI_Mesa version 1
failed to bind extensions
did not find extension DRI_Mesa version 1
failed to bind extensions
[2025-03-25 13:07:24.800] [LOG]   Starting MagicMirror: v2.30.0
[2025-03-25 13:07:24.809] [LOG]   Loading config ...
[2025-03-25 13:07:24.811] [LOG]   config template file not exists, no envsubst
[2025-03-25 13:07:25.425] [INFO]  Checking config file /home/scott/MagicMirror/config/config.js ...
[2025-03-25 13:07:25.451] [INFO]  Your configuration file doesn't contain syntax errors :)
[2025-03-25 13:07:25.451] [INFO]  Checking modules structure configuration ...
[2025-03-25 13:07:25.489] [INFO]  Your modules structure configuration doesn't contain errors :)
[2025-03-25 13:07:25.491] [LOG]   Loading module helpers ...
[2025-03-25 13:07:25.492] [LOG]   No helper found for module: alert.
[2025-03-25 13:07:25.498] [LOG]   Initializing new module helper ...
[2025-03-25 13:07:25.499] [LOG]   Module helper loaded: updatenotification
[2025-03-25 13:07:25.499] [LOG]   No helper found for module: clock.
[2025-03-25 13:07:25.640] [LOG]   Initializing new module helper ...
[2025-03-25 13:07:25.640] [LOG]   Module helper loaded: calendar
[2025-03-25 13:07:25.642] [LOG]   No helper found for module: compliments.
[2025-03-25 13:07:25.647] [LOG]   No helper found for module: weather.
[2025-03-25 13:07:25.761] [LOG]   Initializing new module helper ...
[2025-03-25 13:07:25.762] [LOG]   Module helper loaded: newsfeed
[2025-03-25 13:07:25.762] [LOG]   All module helpers loaded.
[2025-03-25 13:07:25.765] [LOG]   Starting server on port 8089 ...
[2025-03-25 13:07:25.770] [WARN]  You're using a full whitelist configuration to allow for all IPs
[1800:0325/130726.055765:ERROR:wayland_connection.cc(198)] Failed to connect to Wayland display: No such file or directory (2)
[1800:0325/130726.055835:ERROR:ozone_platform_wayland.cc(264)] Failed to initialize Wayland platform
[1800:0325/130726.055842:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.
/home/scott/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

[sdetweil]

@Scott-M this is confusing… by default the system is setup for wayland/labwc,
not x11 (which npm start does)

just another test, using manual install into another folder

cd ~
git clone https://github.com/MagicMirrorOrg/MagicMirror.git fribble
cd fribble
npm run install-mm
npm start 

if that fails then try erasing the saved electron info

cd ~
rm -rf .config/Electron
cd MagicMirror 
npm start 

you try the fribble directory too

[Scott-M]

@sdetweil

Sorry, same result with both of those, doesn’t get past the starting server message.

System info:

sudo cat /sys/firmware/devicetree/base/model;echo
cat /etc/os-release
Raspberry Pi 5 Model B Rev 1.0
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

I do have an SD with a working MagicMirror on it, installed exactly the same was a couple of weeks ago.

I have just going to try another fresh install of bookworm, update / upgrade and then manually install nodejs and npm and MagicMirror ans see what happens. Don’t expect a different result but will see what happens.

[Scott-M]

@Scott-M @sdetweil

So, it works installing manually, bash history…:

sudo apt update
sudo apt full-upgrade
sudo reboot now
curl -sL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install nodejs -y
sudo apt install npm
git clone https://github.com/MagicMirrorOrg/MagicMirror
cd MagicMirror
npm run install-mm
cp config/config.js.sample config/config.js
npm start

The install log from the one that doesn’t run is here if that helps at all.

[sdetweil]

@Scott-M very interesting… only thing I can see different is the sandbox permissions

I don’t have time til later today to examine any more…

thanks for the feedback

[Scott-M]

@sdetweil OK, I will keep the various SD cards with working and non working version for a while just in case it would be of help.

[sdetweil]

@Scott-M thanks… appreciate that

[Scott-M]

@sdetweil

I had one more attempt at this, this time I ran an update and upgrade before running your script and this time it worked. Cannot see why that would be…

Happy to experiment more if you need more info but I am going to start on building the 2 way mirror now!

[sdetweil]

@Scott-M and my script does that before too, its in the install.log file

[Scott-M]

@sdetweil
I am sorry if this has been a wild goose chase and a waste of your time. I flashed the SD card, ran the script several times and it didn’t work, I will try one more time tomorrow and leave it at that.

Random results from repeating the same process are very frustrating.

[sdetweil]

@Scott-M frustrating indeed

but its normal

[Scott-M]

@sdetweil

Results from todays adventures writing Pi images to SD cards…

I don’t really know what, if any difference there could be but I flashed 4 SD cards with the same
64 bit Bookworm image.

2 of them, I just ran the install script and let it update the system. The other 2, I updated / upgraded first. 1 with apt full-upgrade and the other with apt upgrade and then ran the install script.

The first 2 stopped at the same point on the starting server message and the other 2 just worked.

When the system stops at the starting server message, CTRL-C doesn’t do anything so SIGINT is not being picked up.

It may well just be something peculiar to my setup or enviroment.

[sdetweil]

@Scott-M great feedback… I have family stuff most of the day today…

did you do npm install or npm run install-mm

npm run install-mm is more like what I do in the script… which limits what things npm does…

npm install does everything possible

[Scott-M]

I didn’t do either, I just ran your script from first run on the OS on the first 2 cards. On the other 2 cards, on first run of the OS I entered

sudo apt update
sudo apt full-upgrade
bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"

The only difference between them is your script not updating the system. It may all just be a coincidence and someone else with same hardware verifying would be helpful.

[sdetweil]

@Scott-M ah… ok, I don’t do full-upgrade… only upgrade

Use apt upgrade for routine updates when you don't want to risk removing packages. 
Use apt full-upgrade when you need to ensure that all packages are up-to-date, even if it means removing some packages. 
Be cautious when using apt full-upgrade as it can potentially remove packages that you might need. 

but it seems that full-upgrade handles some dependencies NOT handled by upgrade, which seems like a bug to me… whats the point of upgrade if dependencies aren’t handled…

[sdetweil]

@Scott-M if you have a hankering to run another test, run the script from the test branch for next release… it will still get 2.30 , this does full-upgrade

bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/v231/raspberry.sh)”

[Scott-M]

@sdetweil Bear with me, I have run it 3 times now and it seems to freeze / stop during the upgrade, I can’t see where in the upgrade process it is happening so I have modified the script to output to the treminal during the upgrade instead of the log after it has finished and running it locally on the Pi

Will post back later…

I am assuming the ugrade ran into a problem somewhere, I had left it for nearly an hour and progress hadn’t moved.

Update::

I think the issue is that despite having --assume-yes in the apt-get upgrade command it is still stopping and asking :

Configuration file '/etc/xdg/labwc-greeter/autostart'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** autostart (Y/I/N/O/D/Z) [default=N] ? 

But there is no output to terminal so you can’t answer.

[sdetweil]

@Scott-M that lovely problem again… thanks