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.

    updated installer script available for testing

    Scheduled Pinned Locked Moved Solved Troubleshooting
    211 Posts 18 Posters 254.4k Views 19 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 @sdetweil
      last edited by

      @sdetweil this installer script is now the script in 2.10…

      I will close/lock this topic in a couple days

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 1
      • J Offline
        jorgnyg
        last edited by

        Should I install electron with --arch=armv7l ?

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jorgnyg @jorgnyg
          last edited by

          @jorgnyg Yea guess so. Installation fails on rpi zero. So I deleted the electron folder from node_modules, and ran npm install --arch=armv7l electron@3.0.13

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

            @jorgnyg doesn’t fail on my pi 0.

            Can u send me the install.log

            Sam

            How to add modules

            learning how to use browser developers window for css changes

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

              @sdetweil note that we made electron optional. There is no armv6l at node 10
              So we will run in split mode use chromium

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • J Offline
                jorgnyg @sdetweil
                last edited by

                @sdetweil sure thing. Guess this is the most relevant error

                26380 verbose stack Error: electron-chromedriver@1.8.0 install: `node ./download-chromedriver.js`
                26380 verbose stack Exit status 1
                26380 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
                26380 verbose stack     at EventEmitter.emit (events.js:198:13)
                26380 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
                26380 verbose stack     at ChildProcess.emit (events.js:198:13)
                26380 verbose stack     at maybeClose (internal/child_process.js:982:16)
                26380 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
                26381 verbose pkgid electron-chromedriver@1.8.0
                26382 verbose cwd /home/pi/MagicMirror
                26383 verbose Linux 4.19.75+
                26384 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
                26385 verbose node v10.18.1
                26386 verbose npm  v6.13.4
                26387 error code ELIFECYCLE
                26388 error errno 1
                26389 error electron-chromedriver@1.8.0 install: `node ./download-chromedriver.js`
                26389 error Exit status 1
                26390 error Failed at the electron-chromedriver@1.8.0 install script.
                26390 error This is probably not a problem with npm. There is likely additional logging output above.
                26391 verbose exit [ 1, true ]
                
                S 1 Reply Last reply Reply Quote 0
                • S Offline
                  sdetweil @jorgnyg
                  last edited by

                  @jorgnyg the run-start.sh script now handles this problem and launches chromium instead of electron to connect to mm in serveronly mode

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  J 1 Reply Last reply Reply Quote 0
                  • J Offline
                    jorgnyg @sdetweil
                    last edited by

                    @sdetweil got it!

                    1 Reply Last reply Reply Quote 0
                    • J Offline
                      jthirasilpa
                      last edited by

                      Hi - firstly thanks for putting together this installer!

                      I am running Raspbian on RP3b+ as a fresh install using the command

                      curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh | bash

                      Installer indicated successful install of MagicMirror.

                      Using SSH DISPLAY=:0 npm start gives the following error:

                      magicmirror@2.10.1 start /home/jojo/MagicMirror
                      ./run-start.sh

                      No protocol specified

                      (electron:17801): Gtk-WARNING **: 18:36:26.218: cannot open display: :0
                      npm ERR! code ELIFECYCLE
                      npm ERR! errno 1
                      npm ERR! magicmirror@2.10.1 start: ./run-start.sh
                      npm ERR! Exit status 1
                      npm ERR!
                      npm ERR! Failed at the magicmirror@2.10.1 start script.
                      npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

                      npm ERR! A complete log of this run can be found in:
                      npm ERR! /home/jojo/.npm/_logs/2020-01-25T18_36_26_308Z-debug.log

                      Debug log contents are as follows:

                      0 info it worked if it ends with ok
                      1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
                      2 info using npm@6.13.4
                      3 info using node@v10.18.1
                      4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
                      5 info lifecycle magicmirror@2.10.1~prestart: magicmirror@2.10.1
                      6 info lifecycle magicmirror@2.10.1~start: magicmirror@2.10.1
                      7 verbose lifecycle magicmirror@2.10.1~start: unsafe-perm in lifecycle true
                      8 verbose lifecycle magicmirror@2.10.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/jojo/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
                      9 verbose lifecycle magicmirror@2.10.1~start: CWD: /home/jojo/MagicMirror
                      10 silly lifecycle magicmirror@2.10.1~start: Args: [ ‘-c’, ‘./run-start.sh’ ]
                      11 silly lifecycle magicmirror@2.10.1~start: Returned: code: 1 signal: null
                      12 info lifecycle magicmirror@2.10.1~start: Failed to exec start script
                      13 verbose stack Error: magicmirror@2.10.1 start: ./run-start.sh
                      13 verbose stack Exit status 1
                      13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
                      13 verbose stack at EventEmitter.emit (events.js:198:13)
                      13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
                      13 verbose stack at ChildProcess.emit (events.js:198:13)
                      13 verbose stack at maybeClose (internal/child_process.js:982:16)
                      13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
                      14 verbose pkgid magicmirror@2.10.1
                      15 verbose cwd /home/jojo/MagicMirror
                      16 verbose Linux 4.19.75-v7+
                      17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
                      18 verbose node v10.18.1
                      19 verbose npm v6.13.4
                      20 error code ELIFECYCLE
                      21 error errno 1
                      22 error magicmirror@2.10.1 start: ./run-start.sh
                      22 error Exit status 1
                      23 error Failed at the magicmirror@2.10.1 start script.
                      23 error This is probably not a problem with npm. There is likely additional logging output above.
                      24 verbose exit [ 1, true ]

                      Any thoughts on how to troubleshoot? Many thanks.

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

                        @jthirasilpa seems like you are running in console mode, instead of graphical mode.

                        Mm requires the full desktop.

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

                        J 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 15
                        • 16
                        • 17
                        • 18
                        • 19
                        • 20
                        • 21
                        • 22
                        • 17 / 22
                        • 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