@Hepkat yes. We found and fixed this bug just yesterday.
You will need to install the develop branch to get it

See this topic
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

@DDE12 we changed the default for npm start to be Wayland as we documented in the release notes

That is why you have to use npm run start:x11

We also moved user files to the config folder
And moved the default modules to their own folder away from the modules folder

As I posted about a month ago.

How did you upgrade? git pull or my scripted upgrade?

@DDE12 did your css/custom.css file get moved to the config folder?

@Megawaldi it is fixed in the develop branch for next release
You can get the develop branch,

Currently we only release 4 times a year January ,April, July, October

See https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

@magicmikael if you do env

Do you see wayland_display in the list?

The script sets WAYLAND_DISPLAY if not already set

Here is the script , make sure to make it executable
chmod +x mm.sh

#!/bin/bash
cd ~/MagicMirror

if [ $(ps -ef | grep -v grep | grep -i -e xway -e labwc | wc -l) -ne 0 ]; then 
   # if WAYLAND_DISPLAYis set, use it, else set to -0
   export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:=wayland-0}
   npm run start:wayland
else
   DISPLAY=:0 npm run start:x11
fi 

@megagprime try this
module

position:"bottom_left",

no custom.css setting

custom.css

.MMM-CalendarExt3 .module-content {
    width:175%;
}

adjust % as you need

@magicmikael as we said in the readme notes on the release

We changed
npm start/node —run start

To launch for Wayland compositor

If you are still on x11
You need to use

npm run start:x11
Or
node —run start:x11

@megagprime if you just put it in another position , it will be in that positions size, without custom.css
I am away from my system til late us central time tonight

@megagprime you will have to use position absolute and width
You can use the developers window elements tab to try it out.

See the second link in my sig below for an example on how to use the elements tab

@TX77ConfigMirror where are you looking for changes?

@megagprime if you put the module in bottom bar it will resize.

It fits in the area you place it

@SdR awesome. Sorry it took so long. Got sidetracked by the MagicMirror install problem, which wasn’t the cause

@SdR Ok, in 2.35 we rewrote the data collection portion of the weather module
it does NOT support the old version 2.5 openweather api anymore.

so, to use the openweather provider, you must get a new 3.0 apikey from openweather which requires a credit card, and you get (today) 1000 free api calls. (so net free)

from a year ago, in the troubleshooting section

https://forum.magicmirror.builders/topic/19323/version-2.30.0-weather-module-stuck-loading-worked-fine-before-upgrade?page=1

@SdR ok,

do this, stop of there is an error with one command

pm2 stop all
cd ~/MagicMirror
rm -rf node_modules
rm package-lock.json
npm run install-mm
npm run start:x11

@SdR said:

DISPLAY=:0 npm start <----- change this one
fi

#DISPLAY=:0 npm start <— this one is commented out (#)

@SdR >Sun Apr 5 10:08:29 CEST 2026

there was a bug in the upgrade I fixed at 21:00 US Central time

can you edit ~/MagicMirror/installers/mm.sh

and change the

npm start 

to

npm run start:x11

then you can
pm2 restart MagicMirror

@SdR can you show me the end, last 20 lines of the MagicMirror/installers/upgrade.log

@DarrenO-0 I understand. You might be able to switch to a different provider on the weather module, depending on where you are. Not all providers are world wide

@SdR ok. Looks like something added electron/rebuild
And fonts

@Scruffy I strongly recommend using some backup/restore mechanism,
please see my backup/restore scripts for one approach.

they also support versioning, so you can tell one set of changes from another and can go back or forward…
and move between systems. too…

https://github.com/sdetweil/MagicMirror-backup-restore.git

and I also support the install/upgrade scripts, mentioned in the MM doc, Alternative install section