• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
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.3k 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 Away
    sdetweil @Dotmatrix812
    last edited by Apr 28, 2024, 6:22 PM

    @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 Away
      sdetweil @Dotmatrix812
      last edited by Apr 28, 2024, 6:26 PM

      @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

      D 1 Reply Last reply Apr 29, 2024, 5:49 AM Reply Quote 0
      • D Offline
        Dotmatrix812 @sdetweil
        last edited by Apr 29, 2024, 5:49 AM

        @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 Apr 30, 2024, 4:11 PM

          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 Apr 30, 2024, 4:40 PM Reply Quote 0
          • S Away
            sdetweil @tinkertailorgeek
            last edited by Apr 30, 2024, 4:40 PM

            @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 Apr 30, 2024, 6:09 PM Reply Quote 0
            • T Offline
              tinkertailorgeek @sdetweil
              last edited by Apr 30, 2024, 6:09 PM

              @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
              2 / 2
              • First post
                11/16
                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