Read the statement by Michael Teeuw here.
After update, nothing happens.
-
Should I stop that before doing this
"git pull origin develop / npm install --only=prod / npm start "in the old MM?
-
@Richard238 yes pm2 stop all
-
pi@pi_mirror:~ $ pm2 stop all [PM2] Applying action stopProcessId on app [all](ids: 0) [PM2] [mm](0) ✓ ┌──────┬──────┬─────────┬───┬─────┬────────┐ │ Name │ mode │ status │ ↺ │ cpu │ memory │ ├──────┼──────┼─────────┼───┼─────┼────────┤ │ mm │ fork │ stopped │ 0 │ 0% │ 0 B │ └──────┴──────┴─────────┴───┴─────┴────────┘ Use `pm2 show <id|name>` to get more details about an app pi@pi_mirror:~ $ cd ~/MagicMirror__RL1 pi@pi_mirror:~/MagicMirror__RL1 $ git pull origin develop remote: Enumerating objects: 8, done. remote: Counting objects: 100% (8/8), done. remote: Compressing objects: 100% (8/8), done. remote: Total 8 (delta 1), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (8/8), done. From https://github.com/MichMich/MagicMirror * branch develop -> FETCH_HEAD a4ab0cb..da00c16 develop -> origin/develop Updating a4ab0cb..da00c16 Fast-forward CHANGELOG.md | 1 + js/module.js | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) pi@pi_mirror:~/MagicMirror__RL1 $ npm install --only=prod > magicmirror@2.14.0-develop install /home/pi/MagicMirror__RL1 > echo "Installing vendor files ... " && cd vendor && npm install --loglevel=error Installing vendor files ... audited 24 packages in 1.991s 1 package is looking for funding run `npm fund` for details found 0 vulnerabilities > magicmirror@2.14.0-develop postinstall /home/pi/MagicMirror__RL1 > npm run install-fonts && echo "MagicMirror installation finished successfully! " > magicmirror@2.14.0-develop install-fonts /home/pi/MagicMirror__RL1 > echo "Installing fonts ... " && cd fonts && npm install --loglevel=error Installing fonts ... audited 1 package in 1.03s found 0 vulnerabilities MagicMirror installation finished successfully! audited 1149 packages in 36.561s 16 packages are looking for funding run `npm fund` for details found 1 low severity vulnerability run `npm audit fix` to fix them, or `npm audit` for details pi@pi_mirror:~/MagicMirror__RL1 $ npm start > magicmirror@2.14.0-develop start /home/pi/MagicMirror__RL1 > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js /home/pi/MagicMirror__RL1/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror__RL1/node_modules/electron/dist/electron) pi@pi_mirror:~/MagicMirror__RL1 $ -
@sdetweil the new install used the master branch, so on electron 6. the old folder is on develop, so electron 8.5
-
@Richard238 ok. 1st time seeing this…
just to make sure
from the old folder
grep version node_modules/electron/package.json -
@sdetweil said in After update, nothing happens.:
grep version node_modules/electron/package.json
pi@pi_mirror:~/MagicMirror__RL1 $ grep version node_modules/electron/package.json
“type”: “version”,
“version”: “8.5.3”
pi@pi_mirror:~/MagicMirror__RL1 $ -
@sdetweil one more diag command
lsb_release -a
-
pi@pi_mirror:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
pi@pi_mirror:~ $ -
@Richard238 ok, thx. problem is new electron won’t run on Jessie anymore…
I don’t know if this will work.
from. the old mm folder
rm -rf node_modules/electron
npm install electron@6.1.12
then npm start -
@sdetweil said in After update, nothing happens.:
npm install electron@6.1.12
Sam, you’re a genius!
That’s fixed it.
This will only happen again in the not too distant future I’m sure, so would I be better off installing a newer OS?
And then how do I recreate my MM on said new OS?I’m going to logoff for now, thanks again for your help today.
More tomorrow I’m sure.
Kind regards,
Richard.
