MagicMirror² v2.12.0 is available! For more information about this release, check out this topic.

Electron failed to Install error after upgrading to 2.12.0



  • @sdetweil
    I am getting following error after updating to 2.12.0. appreciate any pointers on what I am doing wrong or how to fix the issue. I attempted to reinstall a couple of times.

    pi@raspberrypi:~/MagicMirror $ npm start

    magicmirror@2.12.0 start /home/pi/MagicMirror
    DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

    /home/pi/MagicMirror/node_modules/electron/index.js:14
    throw new Error(‘Electron failed to install correctly, please delete node_modules/electron and try installing again’)
    ^

    Error: Electron failed to install correctly, please delete node_modules/electron and try installing again
    at getElectronPath (/home/pi/MagicMirror/node_modules/electron/index.js:14:11)
    at Object. (/home/pi/MagicMirror/node_modules/electron/index.js:18:18)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions…js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object. (/home/pi/MagicMirror/node_modules/electron/cli.js:3:16)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! magicmirror@2.12.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the magicmirror@2.12.0 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/pi/.npm/_logs/2020-07-08T12_02_15_704Z-debug.log
    pi@raspberrypi:~/MagicMirror $



  • @rahula74 how did u upgrade? my script or manually?

    what pi are u on and what is level?
    run
    lsb_release -a
    for that is info



  • Thanks @sdetweil

    I am on Pi 3 ( I am a novice to MM. where do I run isb_release -a for the info you requested? on the terminal?)

    I used your script to upgrade.



  • @rahula74 issue commands in a terminal window

    can u show me the ~/MagicMirror/installers/upgrade.log



  • @sdetweil
    here is latest upgrade log

    Upgrade started - Wed Jul 8 14:21:46 CDT 2020
    system is Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
    the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
    doing test run = true, NO updates will be applied!

    saving custom.css
    remote name = origin
    upgrading from version 2.12.0 to 2.12.0
    fetching latest revisions
    git fetch rc=0
    current branch = master
    On branch master
    Your branch is up to date with ‘origin/master’.

    Changes not staged for commit:
    (use “git add/rm …” to update what will be committed)
    (use “git checkout – …” to discard changes in working directory)

    deleted:    package-lock.json
    

    Untracked files:
    (use “git add …” to include in what will be committed)

    css/save_custom.css
    run-start.sh
    

    no changes added to commit (use “git add” and/or “git commit -a”)
    no files different from github version
    test merge result rc=’’ , if empty, no conflicts
    skipping merge, only test run
    downloading dumpactivemodules script
    no modules found needing npm refresh
    restoring custom.css
    removing git alias
    Upgrade ended - Wed Jul 8 14:21:51 CDT 2020

    Upgrade started - Wed Jul 8 14:22:11 CDT 2020
    system is Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
    the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
    user requested to apply changes
    doing test run = false

    saving custom.css
    remote name = origin
    local version 2.12.0 already same as master 2.12.0
    restoring custom.css
    removing git alias
    Upgrade ended - Wed Jul 8 14:22:12 CDT 2020



  • @rahula74 use force instead of apply if u tried it manually once



  • @sdetweil
    ok.will give it a try.
    Thanks!



  • @sdetweil
    tried Force. following is the log. no luck though with npm start to launch MM

    Upgrade started - Wed Jul 8 14:29:34 CDT 2020
    system is Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
    the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
    user requested to force apply changes
    doing test run = false

    saving custom.css
    remote name = origin
    upgrading from version 2.12.0 to 2.12.0
    fetching latest revisions
    git fetch rc=0
    current branch = master
    On branch master
    Your branch is up to date with ‘origin/master’.

    Changes not staged for commit:
    (use “git add/rm …” to update what will be committed)
    (use “git checkout – …” to discard changes in working directory)

    deleted:    package-lock.json
    

    Untracked files:
    (use “git add …” to include in what will be committed)

    css/save_custom.css
    run-start.sh
    

    no changes added to commit (use “git add” and/or “git commit -a”)
    no files different from github version
    test merge result rc=’’ , if empty, no conflicts
    executing merge, apply specified
    merge result rc= 0
    Already up to date.
    processor architecture is armv7l
    updating MagicMirror runtime, please wait
    npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
    npm WARN deprecated webdriverio@4.14.4: outdated version, please use @next
    npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
    npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/css-value failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
    npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
    npm WARN deprecated core-js@2.6.11: core-js@ magicmirror@2.12.0 install /home/pi/MagicMirror

    echo "Installing vendor files …
    " && cd vendor && npm install --loglevel=error

    Installing vendor files …

    Upgrade started - Wed Jul 8 15:44:11 CDT 2020
    system is Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
    the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
    user requested to force apply changes
    doing test run = false

    saving custom.css
    remote name = origin
    upgrading from version 2.12.0 to 2.12.0
    fetching latest revisions
    git fetch rc=0
    current branch = master
    On branch master
    Your branch is up to date with ‘origin/master’.

    Changes not staged for commit:
    (use “git add/rm …” to update what will be committed)
    (use “git checkout – …” to discard changes in working directory)

    deleted:    package-lock.json
    

    Untracked files:
    (use “git add …” to include in what will be committed)

    css/save_custom.css
    run-start.sh
    

    no changes added to commit (use “git add” and/or “git commit -a”)
    no files different from github version
    test merge result rc=’’ , if empty, no conflicts
    executing merge, apply specified
    merge result rc= 0
    Already up to date.
    processor architecture is armv7l
    updating MagicMirror runtime, please wait
    npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
    npm WARN deprecated webdriverio@4.14.4: outdated version, please use @next
    npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
    npm WARN deprecated core-js@2.6.11: core-js@ magicmirror@2.12.0 install /home/pi/MagicMirror

    echo "Installing vendor files …
    " && cd vendor && npm install --loglevel=error

    Installing vendor files …

    added 82 packages from 57 contributors and audited 150 packages in 12.974s
    found 8 vulnerabilities (7 low, 1 high)
    run npm audit fix to fix them, or npm audit for details

    magicmirror@2.12.0 postinstall /home/pi/MagicMirror
    npm run install-fonts && echo "MagicMirror installation finished successfully!
    "

    magicmirror@2.12.0 install-fonts /home/pi/MagicMirror
    echo "Installing fonts …
    " && cd fonts && npm install --loglevel=error

    Installing fonts …

    added 1 package from 1 contributor and audited 1 package in 1.285s
    found 0 vulnerabilities

    MagicMirror installation finished successfully!

    npm notice created a lockfile as package-lock.json. You should commit this file.
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.1 (node_modules/chokidar/node_modules/fsevents):
    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“arm”})

    audited 1042 packages in 69.581s

    11 packages are looking for funding
    run npm fund for details

    found 3 low severity vulnerabilities
    run npm audit fix to fix them, or npm audit for details
    npm install completed - Wed Jul 8 15:45:29 CDT 2020 on base
    downloading dumpactivemodules script
    no modules found needing npm refresh
    restoring custom.css
    removing git alias
    Upgrade ended - Wed Jul 8 15:45:30 CDT 2020



  • @rahula74 weird. thanks for the log.
    can you do

    cd ~/MagicMirror
    npm install
    npm start
    


  • @sdetweil
    Thanks Sam.
    I ended up deleting prior installation and used your script to reinstall.
    Its up and running now.
    Thanks again!


Log in to reply