MagicMirror stopped working after screensaver installed

[demetry07]

After I installed the screensaver to stop the screen going dark my MagicMirror stopped working.

I now get this error.

magicmirror@2.10.0 start /home/pi/MagicMirror
./run-start.sh

App threw an error during load
Error: Cannot find module ‘module-alias/register’
at Module._resolveFilename (internal/modules/cjs/loader.js:602:15)
at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
at Function.Module._load (internal/modules/cjs/loader.js:528:25)
at Module.require (internal/modules/cjs/loader.js:658:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (/home/pi/MagicMirror/js/app.js:15:1)
at Object. (/home/pi/MagicMirror/js/app.js:283:3)
at Module._compile (internal/modules/cjs/loader.js:711:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:722:10)
at Module.load (internal/modules/cjs/loader.js:620:32)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module ‘module-alias/register’
at Module._resolveFilename (internal/modules/cjs/loader.js:602:15)
at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
at Function.Module._load (internal/modules/cjs/loader.js:528:25)
at Module.require (internal/modules/cjs/loader.js:658:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (/home/pi/MagicMirror/js/app.js:15:1)
at Object. (/home/pi/MagicMirror/js/app.js:283:3)
at Module._compile (internal/modules/cjs/loader.js:711:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:722:10)
at Module.load (internal/modules/cjs/loader.js:620:32)

[sdetweil]

@demetry07 said in MagicMirror stopped working after screensaver installed:

After I installed the screensaver

what does that mean?

[demetry07]

I installed
apt-get install xscreensaver

[sdetweil]

@demetry07 ok… that should not have affected the mirror in any way…

[demetry07]

I agree but that was all I did.
Installed then disabled making the screen go blank then sudo reboot.

After reboot I get the error I posted above.

[sdetweil]

@demetry07 weird…

please do

cd ~/MagicMirror
npm instal

advise npm start results after

[demetry07]

That fixed it thank you.

[sdetweil]

@demetry07 for the future, I have a script as part of install to disable screensaver on a lot of systems…
its also in the installers folder with 2.10

screensaveroff.sh

[demetry07]

@sdetweil When I ran the install it asked me if I wanted to disable screensaver and I said yes but my screen was still going black over night. I would have to CTRL-Q out then it would run again automatically after a few seconds. Thought installing the screensaver and disabling it would help. Will see after tonight.

[demetry07]

I spoke to soon. This morning it stopped working again.

I ran
npm install
then
sudo reboot
then cd ~/MagicMirror
then
npm start
Here are the results
pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.10.0 start /home/pi/MagicMirror
./run-start.sh

[11:35:13.428] [LOG] Starting MagicMirror: v2.10.0
[11:35:13.448] [LOG] Loading config …
[11:35:13.463] [LOG] Loading module helpers …
[11:35:13.466] [LOG] No helper found for module: alert.
[11:35:13.594] [LOG] Initializing new module helper …
[11:35:13.596] [LOG] Module helper loaded: updatenotification
[11:35:13.597] [LOG] No helper found for module: clock.
[11:35:13.599] [LOG] No helper found for module: currentweather.
/home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js: symbol lookup error: /home/pi/MagicMirror/modules/MMM-PIR/node_modules/epoll/build/Release/epoll.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! magicmirror@2.10.0 start: ./run-start.sh
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.10.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-01-07T17_35_13_737Z-debug.log

I pulled the log file here is the data in the log file.

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.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.10.0~prestart: magicmirror@2.10.0
6 info lifecycle magicmirror@2.10.0~start: magicmirror@2.10.0
7 verbose lifecycle magicmirror@2.10.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.10.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/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.0~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.10.0~start: Args: [ ‘-c’, ‘./run-start.sh’ ]
11 info lifecycle magicmirror@2.10.0~start: Failed to exec start script
12 verbose stack Error: magicmirror@2.10.0 start: ./run-start.sh
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:198:13)
12 verbose stack at maybeClose (internal/child_process.js:982:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
13 verbose pkgid magicmirror@2.10.0
14 verbose cwd /home/pi/MagicMirror
15 verbose Linux 4.19.75-v7+
16 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
17 verbose node v10.18.0
18 verbose npm v6.13.4
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error magicmirror@2.10.0 start: ./run-start.sh
23 error spawn ENOENT
24 error Failed at the magicmirror@2.10.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

Thoughts?