Well, the backup is still working as before. So it is somehow related to the new version 2.11.0

Yes, I have a display_rotate=1 in my /boot/config.txt

But even when I turn it back to 0 and restart the raspberry the issue seems to stay the same.

I’ll try to go back to the previous commit and my backup folder and have a look if the issue vanish or persist. Maybe it’s a driver problem…

Wow, this was a fast reply. Thanks @sdetweil !

Yes, I have a backup from before the upgrade. But the main.css and custom.css are identical to the current version.

There was also no change in my repo which prevented me from a fast forward pull. So I guess there was no change from me which was overwritten by the upgrade.

I’m not familiar with the functionality of npm. Was there maybe some update of another software package?

Hi there!

I need help with the configuration of my display after the upgrade to version 2.11.0

I’m using a Pi 3 Model B+ with an old laptop screen in portrait orientation. As far as I remember there were no problems with the default display sections during the setup of my MagicMirror. Everything ended up where I wanted it to be.

But since the upgrade the different modules are shifted all together and are overlapping. I did a git pull and npm install, run also the npm audit fix and installed the latest Node.js version as described in the Manual Installation guide. I also moved to the standard config.js and made a screenshot to show the issue:

It seems like the lower part of the display is no longer taken into account for the calculation of the display sections.
Has anybody an idea where this could come from and how this could be solved?

I’m happy to provide more information, but at the moment I have no clue where to look for the problem.

uname -a
Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

Thanks for your help!