MagicMirror² v2.14.0 is available! For more information about this release, check out this topic.

Allocation of display sections (e.g. 'lower third' and so on) gives strange results after upgrade to 2.11.0

  • 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!

  • @phil I suspect u had a custom cs file… which got overlayed during the update.
    do you have a backup? if so, you are looking for MagicMirror/css/main.css and custom.css

  • 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?

  • @phil npm is the node package manager

    if you project requires a node library/package, u add it to you projects package.json file and then npm install will read the package.json list and install them (and their dependencies)

    like apt-get for the OS, but just for node apps like MM

    no idea the problem tho… but don’t have any portrait layout systems
    you did the portrait thing as part of the pi setup, right… desktop is vertical after logon…

  • This post is deleted!

  • 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…

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


  • @phil very interesting…

    this version does update electron to v6.1.7

  • I’m not sure if electron is the issue. I tried with several commits and figured out 7b3a594 is still working fine for me, but 6e7edd9 (the one before the “Upgrade to Electron 6”) already causes this problem for me.

    Oh, I just realized there is an electron upgrade already in this commit (although it is not stated in the commit message):

    > electron-chromedriver@6.0.0 install /home/pi/MagicMirror/node_modules/electron-chromedriver
    > node ./download-chromedriver.js
    > electron@6.1.7 postinstall /home/pi/MagicMirror/node_modules/electron
    > node install.js

    So might well be an electron issue. Can you give me some advice how I can try different versions to see which one is working for my setup?

  • @phil erase the node_modules/electron folder
    Then do

    npm install electron@version --only=prod

    The --only keeps from loading the stuff used by testing… like the chromedriver

    I last tested 6.0.12, but don’t know if it was ok for portrait mode use

    U may have to redo npm install in module folders. As many modules depend on electron levels

    All this from the MagicMirror folder

Log in to reply