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.

    Error log full of this error - gdk_monitor_get_scale_factor

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    16 Posts 3 Posters 1.6k Views 4 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.
    • S Offline
      sdetweil @Dotmatrix812
      last edited by

      @Dotmatrix812 here also is an interesting cause

      no monitor attached, Is this your case?

      1000025820.jpg

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      Dotmatrix812D 1 Reply Last reply Reply Quote 0
      • Dotmatrix812D Offline
        Dotmatrix812 @sdetweil
        last edited by

        @sdetweil

        Seems so.

        
        [2024-04-28 20:08:21.486] [INFO]  BACKGROUNDSLIDESHOW: reading path "modules/MMM-BackgroundSlideshow/fotos//1.jpg" 
        [7029:0428/200827.311004:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
        [7029:0428/200827.343752:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
        [7029:0428/200827.350960:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
        [2024-04-28 20:09:21.614] [INFO]  BACKGROUNDSLIDESHOW: reading path "modules/MMM-BackgroundSlideshow/fotos//10.jpg" 
        [2024-04-28 20:10:21.688] [INFO]  BACKGROUNDSLIDESHOW: reading path "modules/MMM-BackgroundSlideshow/fotos//8.jpg" 
        [2024-04-28 20:11:21.762] [INFO]  BACKGROUNDSLIDESHOW: reading path "modules/MMM-BackgroundSlideshow/fotos//12.jpg"
        
        

        Strange that the time stamp is so different …

        1 Reply Last reply Reply Quote 0
        • Dotmatrix812D Offline
          Dotmatrix812 @sdetweil
          last edited by

          @sdetweil

          No. Monitor is connected to the raspberry. Or could this happen when the monitor gets switched off via the MMM-PIR module ?

          Sorry that my answers take so long. But I still need 3 reputations as new user.

          S 2 Replies Last reply Reply Quote 0
          • S Offline
            sdetweil @Dotmatrix812
            last edited by

            @Dotmatrix812 could be because turned off… altho I have not seen this before

            Sam

            How to add modules

            learning how to use browser developers window for css changes

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

              @Dotmatrix812 also, I am the one that approves posts

              they may be delayed as I am spending time w grandson

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              Dotmatrix812D 1 Reply Last reply Reply Quote 0
              • Dotmatrix812D Offline
                Dotmatrix812 @sdetweil
                last edited by

                @sdetweil

                Time with the grandson is very important 👍

                I will check if I can find out if the errors appear after the monitor gets switched off.

                1 Reply Last reply Reply Quote 0
                • T Offline
                  tinkertailorgeek
                  last edited by

                  I have MM v2.27.0 on a Pi 3 running bookworm with a monitor attached and I get the same 3 lines in my npm logs.

                  The Pi is using a PIR to monitor presence and turn off the screen after a fixed period of inactivity from the PIR. The screen is turned off by calling a shell to execute xrandr.

                  I can reproduce the error by issuing the command:

                  DISPLAY=:0.0 xrandr --output HDMI-1 --off
                  

                  while the screen is on. No errors occur if I use the same command and the screen is already off.

                  Hope this helps.

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

                    @tinkertailorgeek thanks… so the code managing the screen doesn’t like having the hdmi channel chopped out from under it…
                    I assume the errors go away when the hdmi port is turned back on

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      tinkertailorgeek @sdetweil
                      last edited by

                      @sdetweil The 3 error entries in the log file only appear at the point in time that the xrandr off is issued. They don’t appear again until the screen has been turned on again and another xrandr -off gets issued.

                      1 Reply Last reply Reply Quote 1
                      • 1
                      • 2
                      • 2 / 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