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

Black screen after Update again

Scheduled Pinned Locked Moved Unsolved Troubleshooting
10 Posts 4 Posters 3.4k Views 5 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
    last edited by Apr 7, 2019, 11:06 AM

    ok, open the developers window

    ctrl-shift-i
    

    and select the console tab, and scroll up to see any errors… usually red text

    Sam

    How to add modules

    learning how to use browser developers window for css changes

    1 Reply Last reply Reply Quote 0
    • T Offline
      thedk
      last edited by thedk Apr 7, 2019, 2:28 PM Apr 7, 2019, 2:02 PM

      This is not possible over a terminal programm?

      The Error is back…

      0|mm       | [9898:0407/121438.093751:FATAL:bus.cc(1151)] D-Bus connection was disconnected. Aborting.
      0|mm       | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
      0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
      0|mm       | npm ERR! code ELIFECYCLE
      0|mm       | npm ERR! errno 1
      0|mm       | npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
      0|mm       | npm ERR! Exit status 1
      0|mm       | npm ERR!
      0|mm       | npm ERR! Failed at the magicmirror@2.7.1 start script.
      0|mm       | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
      0|mm       |
      0|mm       | npm ERR! A complete log of this run can be found in:
      0|mm       | npm ERR!     /home/pi/.npm/_logs/2019-04-07T10_21_07_746Z-debug.log
      0|mm       | XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
      0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.
      
      
      1 Reply Last reply Reply Quote 0
      • T Offline
        thedk
        last edited by Apr 10, 2019, 5:47 PM

        The black screen was my fault :(
        I did a lil mistake. After setting up a other Pi with MMM and copying my config i had the same problem. So i was checking my config (no syntax error), and everything i could rember was, that i changed this:

        var config = {
                address: "localhost",                   // Address to listen on, can be:
                                                        // - "localhost", "127.0.0.1", $
                                                        // - another specific IPv4/6 to$
                                                        // - "", "0.0.0.0", "::" to lis$
                                                        // Default, when address config$
                port: 8080,
                address: "0.0.0.0",
                ipWhitelist: [],
        

        to this:

        var config = {
                address: ["localhost", "0.0.0.0"],                  // Address to listen on, can be:
                                                        // - "localhost", "127.0.0.1", $
                                                        // - another specific IPv4/6 to$
                                                        // - "", "0.0.0.0", "::" to lis$
                                                        // Default, when address config$
                port: 8080,
                ipWhitelist: [],
        

        And that was everything and cost me a lot of time ^^

        1 Reply Last reply Reply Quote 0
        • C Offline
          cowboysdude Module Developer
          last edited by Jun 15, 2019, 2:36 AM

          NEVER NEVER NEVER NEVER DO an update until you’ve backed everything up… THIS solves the problem if the update gets stuck or doesn’t work you just copy over your backup and you’re up and running again…

          S 1 Reply Last reply Jun 15, 2019, 2:47 AM Reply Quote 2
          • S Offline
            sdetweil @cowboysdude
            last edited by Jun 15, 2019, 2:47 AM

            @cowboysdude AND backup OFF the memory card… I lost a whole bunch of stuff when we had 5 power failures back to back… 15 seconds each… memory card did not recover…

            luckily I had a ‘close’ backup… still wasted a couple days…

            now all systems on battery backup

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            M 1 Reply Last reply Jun 16, 2019, 1:02 AM Reply Quote 0
            • M Offline
              Mykle1 Project Sponsor Module Developer @sdetweil
              last edited by Jun 16, 2019, 1:02 AM

              @sdetweil said in Black screen after Update again:

              I lost a whole bunch of stuff when we had 5 power failures back to back… 15 seconds each… memory card did not recover…

              Yikes! :-(

              Create a working config
              How to add modules

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