MM Starts but no screen after upgrade

[geekhouri]

Hi all,

I’m relatively new to MM and typically rely on step-by-step guidance to navigate through tasks. Recently, I successfully created a solid MM setup and was satisfied with it. However, when I decided to upgrade due to the system indicating available updates, things took a turn. Post-upgrade, MM is no longer visible, and I’m struggling to pinpoint the problem. I suspect the issue may be related to the outdated instructions I followed for reference.

"@PaulB First, make a backup of your install with cp -r ~/MagicMirror ~/MM-Backup. Then run git stash in ~/MagicMirror to temporarily stash your changes so that git can merge all those new commits.

To merge, run git pull to update your MM install, then use npm install to upgrade or install any new dependencies to the appropriate version.

Once complete, run git stash apply to reintroduce your changes (while also keeping them in the stash) – you may need to deconflict or otherwise review these changes. You can see your changes with git diff.

Once you’re happy and MM is running smoothly, you can git stash drop to get rid of the stash. You can run rm -rf ~/MM-Backup once you’re content it’s all working as it should.

Finally, I recommend you take the opportunity to also run sudo apt-get update && sudo apt-get dist-upgrade npm && sudo dist-upgrade pm2 (I think nodejs should upgrade as a dependency of npm but could be wrong)."

GIT STATUS output is:

On branch master
Your branch is up to date with ‘origin/master’.

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

nothing added to commit but untracked files present (use “git add” to track)

Any help to resolve would be appreciated before i give up and start form scratch again…

Thanks in advance.

George

[sdetweil]

@geekhouri

lets start at the beginning… how did you install, and how did you upgrade?

manual or with my scripts?

tell me output of

node -v
npm -v
lsb_release -a
uname -a

do you use pm2 to autostart?

if so do

pm2 stop all
cd ~/MagicMirror
npm start 

ctrl-q to stop MM

post the error messages

[geekhouri]

HI @sdetweil, Please see answers below:

lets start at the beginning… how did you install, and how did you upgrade? manual or with my scripts? It was manual as per the instructions above

tell me output of

**node -v**  = v20.5.1

**npm -v** = 9.8.0

**lsb_release -a**
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

**uname -a**
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux


**do you use pm2 to autostart?**  Yes i do
> 
**> if so do 
> ```bash
> pm2 stop all
> cd ~/MagicMirror
> npm start 
> ```
> ctrl-q to stop MM
> 
> post the error messages**

@raspberrypi:~/MagicMirror $ npm start

> magicmirror@2.26.0 start
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

[08.01.2024 15:54.29.488] [LOG]   Starting MagicMirror: v2.26.0
[08.01.2024 15:54.29.500] [LOG]   Loading config ...
[08.01.2024 15:54.29.510] [DEBUG] config template file not exists, no envsubst
[08.01.2024 15:54.29.523] [LOG]   Loading module helpers ...
[08.01.2024 15:54.29.526] [LOG]   No helper found for module: alert.
[08.01.2024 15:54.29.604] [LOG]   Initializing new module helper ...
[08.01.2024 15:54.29.606] [LOG]   Module helper loaded: updatenotification
[08.01.2024 15:54.29.608] [LOG]   No helper found for module: clock.
[08.01.2024 15:54.30.088] [LOG]   Initializing new module helper ...
[08.01.2024 15:54.30.090] [LOG]   Module helper loaded: calendar
[08.01.2024 15:54.30.093] [LOG]   No helper found for module: compliments.
[08.01.2024 15:54.31.047] [LOG]   Initializing new module helper ...
[08.01.2024 15:54.31.048] [LOG]   Module helper loaded: MMM-DailyBibleVerse
[08.01.2024 15:54.31.175] [LOG]   Initializing new module helper ...
[08.01.2024 15:54.31.176] [LOG]   Module helper loaded: MMM-OpenWeatherMapForecast
[08.01.2024 15:54.31.178] [LOG]   No helper found for module: MMM-GoogleTrafficTimes.
[08.01.2024 15:54.31.189] [ERROR] (node:1960) UnhandledPromiseRejectionWarning: Error: Cannot find module 'request'
Require stack:
- /home/gkhouri/MagicMirror/modules/MMM-WordOfTheDay/node_helper.js
- /home/gkhouri/MagicMirror/js/app.js
- /home/gkhouri/MagicMirror/js/electron.js
- /home/gkhouri/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js
-
   at node:internal/modules/cjs/loader:1084:15
   at Function.<anonymous> (node:electron/js2c/browser_init:2:116646)
   at Module._resolveFilename (/home/gkhouri/MagicMirror/node_modules/module-alias/index.js:49:29)
   at node:internal/modules/cjs/loader:929:27
   at Function._load (node:electron/js2c/asar_bundle:2:13327)
   at Module.require (node:internal/modules/cjs/loader:1150:19)
   at require (node:internal/modules/cjs/helpers:121:18)
   at Object.<anonymous> (/home/gkhouri/MagicMirror/modules/MMM-WordOfTheDay/node_helper.js:9:15)
   at Module._compile (node:internal/modules/cjs/loader:1271:14)
   at Object..js (node:internal/modules/cjs/loader:1326:10)
   at Module.load (node:internal/modules/cjs/loader:1126:32)
   at node:internal/modules/cjs/loader:967:12
   at Function._load (node:electron/js2c/asar_bundle:2:13327)
   at Module.require (node:internal/modules/cjs/loader:1150:19)
   at require (node:internal/modules/cjs/helpers:121:18)
   at loadModule (/home/gkhouri/MagicMirror/js/app.js:181:19)
(Use `electron --trace-warnings ...` to show where the warning was created)
[08.01.2024 15:54.31.191] [ERROR] (node:1960) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

[sdetweil]

@geekhouri yep,

we’ve been cleaning up the mm core tubing for 2 years now. this module was using one of the libraries we supplied, but didn’t declare it.

if you had used my upgrade script I would have handled this problem for you

see

https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

in the module folder do

npm install request

[geekhouri]

@sdetweil really appreciate your help, that has worked. I will definitely follow your guides moving forward. Out of curiosity when i ran that command i got the following :

pm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142

added 32 packages in 18s

196 packages are looking for funding
run npm fund for details

Do i need do anything here or can i ignore?

[sdetweil]

@geekhouri nothing we/you can do. a library uses a library which uses a library which was upgraded. but we can’t make anyone upgrade, and mm is a special env. it’s not a public website doing banking. it’s just showing some info pulled into. your house .

so, all you can go is ignore it. oh, and don’t do audit fix. it forces a bunch of changes, some of which break existing code, with no fix available.

[geekhouri]

@sdetweil thank-you very much, really appreciate the support on this…

[KristjanESPERANTO]

I have sleep problems and have therefore found the time to get rid of the dependency on request for this module 😅. Let’s see when @jmwyds accepts my PR. It seems he hasn’t been active for a while.