@sdetweil
I switched back to X11 in raspi-config, rebooted and added the parameter
DISPLAY=:0 npm run start:x11
That works! :-)
As it is quite after midnight here, I’ll do these tests with wayland tomorrow and respond here.
So far, thank you a lot.
@sdetweil I used your scripts.
After Upgrade I switched to wayfire in raspi-config and rebooted.
But I can try to get back to X11 and try the additional parameter (:x11).
Two of the modules had updates. I updated these (git pull && npm install).
@sdetweil ok, understood.
I updated my 3 additional modules but still get
~/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP
If i switch to
DISPLAY=:0 npm run server
it starts and I can see the webpage in a browser, but no screen on my mirror. Here only the graphical desktop.
What else can I do or check?
After doing some more research I also updated my 3 additional modules manually.
I thought the update script would also have done this , but it seems it didn’t. The module MMM-homeassistant-sensors wasn’t up to date.
Now it ends with this message
[2026-04-21 22:26:11.173] [LOG] [app] Starting MagicMirror: v2.35.0
[2026-04-21 22:26:11.199] [LOG] [utils] Loading config ...
[2026-04-21 22:26:11.212] [INFO] [utils] Checking config file /home/somename/MagicMirror/config/config.js ...
[2026-04-21 22:26:11.444] [INFO] [utils] Your configuration file doesn't contain syntax errors :)
[2026-04-21 22:26:11.446] [INFO] [utils] Checking modules structure configuration ...
[2026-04-21 22:26:11.643] [INFO] [utils] Your modules structure configuration doesn't contain errors :)
[2026-04-21 22:26:12.799] [LOG] [MMM-homeassistant-sensors] MMM-homeassistant-sensors helper started...
[2026-04-21 22:26:12.801] [LOG] [MMM-MQTT] MMM-MQTT: Starting node helper
[2026-04-21 22:26:13.859] [INFO] [systeminformation]
#### System Information ####
- SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.2; virtual: false; MM: v2.35.0
- OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.75+rpt-rpi-v8
- VERSIONS: electron: 41.1.0; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14
- ENV: XDG_SESSION_TYPE: tty; MM_CONFIG_FILE: undefined
WAYLAND_DISPLAY: wayland-1; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
- RAM: total: 3795.80 MB; free: 3025.94 MB; used: 769.87 MB
- OTHERS: uptime: 75 minutes; timeZone: Europe/Berlin
/home/somename/MagicMirror/node_modules/electron/dist/electron exited with signal SIGTRAP
My mm.sh contains
cd ./MagicMirror
export ELECTRON_DISABLE_GPU=1
export NODE_EXTRA_CA_CERTS=/home/somename/.step/certs/root_ca.crt
DISPLAY=:0 npm start
Is there something else missing?
Hi everyone,
after my mirror run without any issued for a long time, it still stopped working right now, after I did an upgrade from 2.33.0 to 2.35.0 with the upgrade scripts provided by @sdetweil.
I’m running
Linux 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/Linux
on a Raspi 4.
Previous the upgrade, 2.33.0 was running.
I had to switch from X11 to Wayland in raspi-config to avoid these messages
[3525:0421/204946.469269:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
[3525:0421/204946.470022:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:281] Failed to initialize Wayland platform
[3525:0421/204946.470333:ERROR:ui/aura/env.cc:246] The platform failed to initialize. Exiting.
but this error still remains and I do not know how to solve it.
[2026-04-21 20:49:46.375] [ERROR] [unknown] (node:3525) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `electron --trace-deprecation ...` to show where the warning was created)
After this and the info about the system the script terminates.
Any help is welcome.
Regards
Ok, I can reproduce this correction too! :-)
After changing address: “0.0.0.0” to the real ip address: “192.168.x.y” and removing every additional config from this thread ALL images are back again!
Thank you all for this simple but effictive solution!
@sdetweil, @Snille
same here.
The urls to the icons work in browser sessions showing MM, but do not work local in raspi with MM.
I tested access from raspi console with
curl -sL http://<ma-ha-url>:8123/local/images/person.jpg >person.jpg
and this works too.
I also have the same problem, the local MM is not able to access a remote_compliments.conf file via URL in the local module\defaults\compliments folder, but I can access it from a browser. Seems to be the same problem!?
@karsten13
Ok, tried this new config, but it does not change anything. :-(
@Snille said in MMM-homeassistant-sensors no icons after MM upgrade to 2.19.0:
icons: [{ "default": "https://www.snille.net/img/magicmirror/users/jane.png" }]
(think in the example there is one closing bracket missing “]”)
Had the time right now to test this one issue. I insertet the URL to the image from ha :-) (which is a static one here)
http://<my-ha-url>:8123/local/images/hem.png
but after restart of MM the problem still exists.
@karsten13 , @Snille
Sorry for the delay, but hanks for your feedback.
Yes, I’m running MM on a raspi 3.
One more point I figured out:
The display connected to the raspi an showing THE mm on the wall has these problems with missing images.
If I connect with a browser from my desltop to the mm URL the images are visible.
I’ll try to test your given notes this weekend and return the results back here.
Hi everyone,
our MM was running like a charm with 2.18.0 and MMM-homeassistant-sensors from @snille showing our family members and fuel prices with the icons configured in Home Assistant.
After the upgrade to 2.19.0 (and some manual tweaks with other modules) everything is up and running again, but the same elements provided by ha as before do not show up any icons (in fromt of the entries!). At the moment it looks like this:
Normally there should be pictures from our family members and logos from the fuel stations and all comes from ha.
Is there a way to fix this?
What more infos do you need to find what’s going wrong here?
Any help welcome.
Regards
Hi @all,
I’m running my MM for a while (now @ v2.16.0), but since the update, the formating for calender seems to has changed.
I run 3 (default) calendars, the upper two with whole width of the column, the third in the left column of two.
I did some adjustments in custom.css for format my calendars.
I tried to get the same column with for the symbol col and symbol an title left aligned. But there are some spaces, I do not how to resize them.
It now looks like this
But I would like to get the red areas all same width.
For testing I colored the fields and they show up like this
Why are the title fields of the upper two calendars different?
These are my custom.css entries for calendars
/* Calendar Einträge - Symbol */
.calendar .symbol {
font-size: 30px;
text-align: left;
width: 34px;
}
/* Calendar Einträge - Text */
.calendar .title {
font-size: 36px;
text-align: left;
line-height: 40px;
}
/* Calendar Einträge - Zeitpunkt */
.calendar .time {
font-size: 36px;
line-height: 40px;
color: #dddddd; /* white! */
}
Some advices?
How do I align symbol and title to the left?
Is there a way to get this without custom.css?
What is the correct way to control the size of the fields and the size of the space between?
@ah4x4
I had the same problem which was solved today by @sdetweil. It seems to be a bug, see here how to correct it manually, before it ends in the release:
https://github.com/MichMich/MagicMirror/issues/2629#issuecomment-899548844
Second point, if you do not want a countdown but the real dates for future events, set
urgency: 0
as additional parameter in calender config.
All the parameters are described here https://docs.magicmirror.builders/modules/calendar.html
@sdetweil
yes, this is the only module I’m using that generates a graph/chart.
My config.js is sent to you by mail.
@sdetweil here first test results:
If i disable your MyCovid19 modules (both of the two active) the system runs without crashing.
I reduced config step by step to only these three modules (only configured one of each)
How to look further?
@sdetweil ok, I’m going to test this with one module and going to enable one by one…
@sdetweil reran script with force, but still same issue
@sdetweil
No, this time i did it manually. I used it for upgrading my first card (from first post).
Can I use it now for a second time now?