MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

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

    Scheduled Pinned Locked Moved Troubleshooting
    15 Posts 2 Posters 2.7k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      phil
      last edited by

      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:

      1569539256498.remmina-2020-4-9-19:50:54,871535.png

      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!

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @phil
        last edited by

        @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

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 0
        • P Offline
          phil
          last edited by

          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?

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @phil
            last edited by

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

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            1 Reply Last reply Reply Quote 0
            • P Offline
              phil
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • P Offline
                phil
                last edited by

                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.

                1569539256498.remmina-2020-4-9-21:5:31,807371.png

                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…

                1 Reply Last reply Reply Quote 0
                • P Offline
                  phil
                  last edited by

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

                  1569539256498.remmina-2020-4-9-21:46:16,173352.png

                  S 1 Reply Last reply Reply Quote 0
                  • S Offline
                    sdetweil @phil
                    last edited by

                    @phil very interesting…

                    this version does update electron to v6.1.7

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    1 Reply Last reply Reply Quote 0
                    • P Offline
                      phil
                      last edited by

                      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?

                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        sdetweil @phil
                        last edited by sdetweil

                        @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

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 1 / 2
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy