SOLVED Manual installation error
-
Hi all,
New to MagicMirror and this is my first attempt to run it.
It is installed on a Rpi 3B+ with the latest Raspberry OS (2021-05-07-raspios-buster-armhf) and I used the manual installation method as per instructions.
When I try to run MM, this is what I get:alex@MagicMirror:~/MagicMirror $ npm run start > magicmirror@2.16.0 start /home/alex/MagicMirror > electron js/electron.js [13.09.2021 12:34.16.087] [LOG] Starting MagicMirror: v2.16.0 [13.09.2021 12:34.16.096] [LOG] Loading config ... [13.09.2021 12:34.16.110] [LOG] Loading module helpers ... [13.09.2021 12:34.16.114] [LOG] No helper found for module: alert. [13.09.2021 12:34.16.436] [LOG] Initializing new module helper ... [13.09.2021 12:34.16.439] [LOG] Module helper loaded: updatenotification [13.09.2021 12:34.16.441] [LOG] No helper found for module: clock. [13.09.2021 12:34.16.700] [LOG] Initializing new module helper ... [13.09.2021 12:34.16.702] [LOG] Module helper loaded: calendar [13.09.2021 12:34.16.704] [LOG] No helper found for module: compliments. [13.09.2021 12:34.16.706] [LOG] No helper found for module: weather. [13.09.2021 12:34.16.749] [LOG] Initializing new module helper ... [13.09.2021 12:34.16.750] [LOG] Module helper loaded: newsfeed [13.09.2021 12:34.16.752] [LOG] All module helpers loaded. [13.09.2021 12:34.16.913] [LOG] Starting server on port 8080 ... [13.09.2021 12:34.16.942] [LOG] Server started ... [13.09.2021 12:34.16.944] [LOG] Connecting socket for: updatenotification [13.09.2021 12:34.16.946] [LOG] Connecting socket for: calendar [13.09.2021 12:34.16.947] [LOG] Starting node helper for: calendar [13.09.2021 12:34.16.949] [LOG] Connecting socket for: newsfeed [13.09.2021 12:34.16.950] [LOG] Starting node helper for: newsfeed [13.09.2021 12:34.16.952] [LOG] Sockets connected & modules started ... /home/alex/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! magicmirror@2.16.0 start: `electron js/electron.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the magicmirror@2.16.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/alex/.npm/_logs/2021-09-13T11_34_17_115Z-debug.log alex@MagicMirror:~/MagicMirror $Initially I had a different error and I thought I’d follow the troubleshooting instructions saying to change
"start": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js",to
"start": "node_modules/.bin/electron js/electron.js",which I did. Now I am getting the above error.
I checked the debug log and here’s what it contains:0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'start' ] 2 info using npm@6.14.15 3 info using node@v14.17.6 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle magicmirror@2.16.0~prestart: magicmirror@2.16.0 6 info lifecycle magicmirror@2.16.0~start: magicmirror@2.16.0 7 verbose lifecycle magicmirror@2.16.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.16.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/alex/MagicMirror/node_modules/.bin:/usr/local/sb$ 9 verbose lifecycle magicmirror@2.16.0~start: CWD: /home/alex/MagicMirror 10 silly lifecycle magicmirror@2.16.0~start: Args: [ '-c', 'electron js/electron.js' ] 11 silly lifecycle magicmirror@2.16.0~start: Returned: code: 1 signal: null 12 info lifecycle magicmirror@2.16.0~start: Failed to exec start script 13 verbose stack Error: magicmirror@2.16.0 start: `electron js/electron.js` 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:400:28) 13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:400:28) 13 verbose stack at maybeClose (internal/child_process.js:1055:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) 14 verbose pkgid magicmirror@2.16.0 15 verbose cwd /home/alex/MagicMirror 16 verbose Linux 5.10.60-v7+ 17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start" 18 verbose node v14.17.6 19 verbose npm v6.14.15 20 error code ELIFECYCLE 21 error errno 1 22 error magicmirror@2.16.0 start: `electron js/electron.js` 22 error Exit status 1 23 error Failed at the magicmirror@2.16.0 start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]I don’t quite understand what this means. Anyone have any idea how to fix this please?
-
@sdetweil Yes, full version with desktop.
Just deleted the whole MagicMirror folder and run your script.
It works PERFECTLY!I don’t know why this isn’t the default was of installation, it’s sooooo easier!
Thank you for your assistance, much appreciated. -
Perhaps I should also mention that during the installation process, I noticed a warning saying:
“this version of npm is compatible with lockfileVersion@1 but package-lock.json was generated for lockfileVersion@2”
I don’t know if this helps someone but I thought I’d mention it just in case.
-
@dodo you are using the full desktop version of buster, correct?
you should see the temples on the desktop before installing MagicMirror
-
@dodo you could also use my installation script
-
@sdetweil Thank you for that, I’ll try it.
Do I need to uninstall everything and then run your scripts?
Also, I have installed MM using the user “alex” instead of “pi”. Do I need to change anything in your scripts before I run them? -
@dodo just rename the MagicMirror folder to some other name
u only need to run the install script
it should handle different user name just fineu didn’t answer about the os version. needs to be full with graphical desktop
-
@sdetweil Yes, full version with desktop.
Just deleted the whole MagicMirror folder and run your script.
It works PERFECTLY!I don’t know why this isn’t the default was of installation, it’s sooooo easier!
Thank you for your assistance, much appreciated. -
@dodo said in Manual installation error:
I don’t know why this
it’s listed as one of the alternative ways
-
@sdetweil Yeah, I know. It should be the opposite, this method should be the default for dummies like myself!
-
@dodo said in Manual installation error:
should be the default for dummies like myself!
not dummy, just inexperienced…
my script was from the base, but it wasn’t possible to update as frequently as we all needed.
my intent is to get you up and running.
a year from now you will know a lot more
