@sdetweil
Touch screen is now working.
Currently have a micro-hdmi adapter into the RPi. A powered hdmi to usb-c connecting from adapter to the monitor.
The powered bit is plugged into the usb a port on the Pi. Hope this helps in the future 😀

@sdetweil great, I will leave it as is for now otherwise I will go crazy (or more so). I think I might do the same, most of our photos are on a synology nais so would prefer that anyway, so will try that instead 😀

Thank you so much for all your help and patience!!!

@sdetweil err yeah I forgot about that! Tried it and comes up with a lot of these:

[22794:0803/092318.972480:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
[22794:0803/092318.973024:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)

so then ran

npm run start:wayland

and I get:

[22972:0803/092452.875681:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:191] Failed to connect to Wayland display: No such file or directory (2)
[22972:0803/092452.875799:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:278] Failed to initialize Wayland platform
[22972:0803/092452.875834:ERROR:ui/aura/env.cc:257] The platform failed to initialize.  Exiting.
/home/admin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

I then did:

pm2 stop 0
pm2 start 0  //I let it fully load
pm2 stop 0
pm2 logs --err

and I got the following:

0|MagicMir | [2025-08-03 09:26:50.192] [WARN]  You're using a full whitelist configuration to allow for all IPs
0|MagicMir | /home/admin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT

Is this just okay to leave as is? If I hadn’t been checking for other errors, I wouldn’t have known this was popping up as my screen is displaying as expected.

@sdetweil I did a search for it and it and followed instructions, but the GPU memory was not in the raspi-config. Turns out newer RPi5 does not have it.
Found another page on how to change it on the config.txt but I cannot see it listed. File was not in the folder google suggested, so opened the file that the command prompt said it moved.
I am not really set on having ISS-Live, it does work, but whilst I try and work out how to get google photos or other photos, thought it would be nice to see what it could do.
The modules I want seem to be showing okay, but will keep an eye on it.

@sdetweil
I tried to find the config file to see and it was in boot/firmware/config.txt but couldn’t see any reference to GPU. however, I ran what you suggested and got the following:

admin@raspberrypihome:~ $ export ELECTRON_ENABLE_GPU=1
admin@raspberrypihome:~ $ npm start
npm error code ENOENT
npm error syscall open
npm error path /home/admin/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or director
admin/package.json'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /home/admin/.npm/_logs/2025-08-
Z-debug-0.log

Hope this makes sense.

I’m pre-empting you asking about that log, here is the last one:

0 verbose cli /usr/local/bin/node /usr/local/bin/npm
1 info using npm@10.9.2
2 info using node@v22.17.1
3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc
4 silly config load:file:/home/admin/.npmrc
5 silly config load:file:/usr/local/etc/npmrc
6 verbose title npm start
7 verbose argv "start"
8 verbose logfile logs-max:10 dir:/home/admin/.npm/_logs/2025-08-02T07_50_53_293Z-
9 verbose logfile /home/admin/.npm/_logs/2025-08-02T07_50_53_293Z-debug-0.log
10 silly logfile start cleaning logs, removing 1 files
11 silly logfile done cleaning log files
12 verbose stack Error: Could not read package.json: Error: ENOENT: no such file or directory, open '/home/admin/package.json'
12 verbose stack     at async open (node:internal/fs/promises:639:25)
12 verbose stack     at async readFile (node:internal/fs/promises:1243:14)
12 verbose stack     at async read (/usr/local/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/read-package.js:9:18)
12 verbose stack     at async PackageJson.load (/usr/local/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:131:31)
12 verbose stack     at async PackageJson.normalize (/usr/local/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:117:5)
12 verbose stack     at async #run (/usr/local/lib/node_modules/npm/lib/commands/run-script.js:86:13)
12 verbose stack     at async RunScript.exec (/usr/local/lib/node_modules/npm/lib/commands/run-script.js:40:7)
12 verbose stack     at async Npm.exec (/usr/local/lib/node_modules/npm/lib/npm.js:207:9)
12 verbose stack     at async module.exports (/usr/local/lib/node_modules/npm/lib/cli/entry.js:74:5)
13 error code ENOENT
14 error syscall open
15 error path /home/admin/package.json
16 error errno -2
17 error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/home/admin/package.json'
18 error enoent This is related to npm not being able to find a file.
18 error enoent
19 verbose cwd /home/admin
20 verbose os Linux 6.12.34+rpt-rpi-2712
21 verbose node v22.17.1
22 verbose npm  v10.9.2
23 verbose exit -2
24 verbose code -2
25 error A complete log of this run can be found in: /home/admin/.npm/_logs/2025-08-02T07_50_53_293Z-debug-0.log

But at least my screen is populating fine :)

@sdetweil

Hi, sorry running around after kids!

This is the end of the upgrade.log (not sure how my other reply separated!)

Upgrade started - Sat Aug  2 10:11:26 AEST 2025
system is Linux raspberrypihome 6.12.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64 GNU/Linux
user requested to apply changes
doing test run = false
the os is PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/"
architecture from dpkg is 
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v22.17.1
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v22.17.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.2
Installed npm version: V10.9.2
No npm upgrade necessary.

increasing swap space
saving custom.css
remote name = origin
local version 2.32.0 already same as master 2.32.0
restoring custom.css
removing git alias
Upgrade ended - Sat Aug  2 10:11:26 AEST 2025

Re: Accessing config.js and file explorer on laptop

Just an addition to my response which is waiting approving, I put the MMM-worldclock back in and there were no additional errors, I then did the same for the MMM-ISS-Live and get the following error:

0|MagicMir | [10273:0802/102811.267692:ERROR:gpu/command_buffer/service/gles2_cmd_decoder_passthrough.cc:1095] [GroupMarkerNotSet(crbug.com/242999)!:A03058003C000000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader (about:flags#enable-unsafe-swiftshader) flag to opt in to lower security guarantees for trusted content.

Should I post this as a separate post for the module? I now seem to have a handle on how to work out what errors are occuring even if I don’t know how to fix it!!
:)

@sdetweil you must be getting very sick of me!
Those scripts you gave me have been fantastic. I’ve also made my own change log to track my changes to the config file and will do the same with custom.css once I get started.

I added a world clock and the ISS space station module and started getting some errors. I have managed to remove most, and going to slowly apply things again. Currently both are commented out on the config file for the time being so I can isolate the issue.

I am now left with two, one is the ipWhiteList warning, which is fine and then I get the following:

0|MagicMir | /home/admin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT

I did a search and since then I have updated Raspian, I have run your script:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply

but I still have it.
If it helps pm2 -v is 6.0.8, npm -v is 10.9.2, node -v is 22.17.1

p.s. thanks for fixing the ‘code’ in one of my previous replies, I’m being extra careful to mark up codes.

@sdetweil right that’s great and really helpful. The more I am learning, the more I am realising I wasnt quite using the right commands. I’ve tested doing a small change and seems no errors. When I get back I will test making changes through Bitvise and all going well, will go ahead and make lots of changing.
Thank you so much!!

Okay, so I have been doing a bit of testing and trying to work out what is happening and when. Sort of worked out where to check logs and which logs and using a combination of the main terminal, Bitvise and Raspberry Pi Connect to try different things. I think some of the issues, might be related to how I am interacting with it.

I have reinstalled RPiOS and MagicMirror. I have also set up the autostart using pm2. This seems to run and open MM with no errors.

If I was to add a module or change the config file, I would then use

npm run start

to run the MM. I have also started using

npm run start:wayland

helps with some things, but having port issues. I am guessing that this might be due to the autostart and I am not sure how to stop MM running when I am developing it. I had used ctrl_Q, but MM just reruns. Or is that all I need to do?

I am finding that if I turn off the RPi and then turn it on, MM runs with no issues. If I try to run it using the above npm command, I get the following errors:

admin@raspberrypihome:~ $ cd MagicMirror
admin@raspberrypihome:~/MagicMirror $ npm run start:wayland

> magicmirror@2.32.0 start:wayland
> WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland

[2025-08-01 06:24:34.441] [LOG]   Starting MagicMirror: v2.32.0 
[2025-08-01 06:24:34.452] [LOG]   Loading config ... 
[2025-08-01 06:24:34.453] [LOG]   config template file not exists, no envsubst 
[2025-08-01 06:24:34.654] [INFO]  Checking config file /home/admin/MagicMirror/config/config.js ... 
[2025-08-01 06:24:34.690] [INFO]  Your configuration file doesn't contain syntax errors :) 
[2025-08-01 06:24:34.691] [INFO]  Checking modules structure configuration ... 
[2025-08-01 06:24:34.728] [INFO]  Your modules structure configuration doesn't contain errors :) 
[2025-08-01 06:24:34.729] [LOG]   Loading module helpers ... 
[2025-08-01 06:24:34.730] [LOG]   No helper found for module: alert. 
[2025-08-01 06:24:34.733] [LOG]   Initializing new module helper ... 
[2025-08-01 06:24:34.733] [LOG]   Module helper loaded: updatenotification 
[2025-08-01 06:24:34.734] [LOG]   No helper found for module: clock. 
[2025-08-01 06:24:34.794] [LOG]   Initializing new module helper ... 
[2025-08-01 06:24:34.794] [LOG]   Module helper loaded: calendar 
[2025-08-01 06:24:34.795] [LOG]   No helper found for module: compliments. 
[2025-08-01 06:24:34.795] [LOG]   No helper found for module: weather. 
[2025-08-01 06:24:34.830] [LOG]   Initializing new module helper ... 
[2025-08-01 06:24:34.831] [LOG]   Module helper loaded: newsfeed 
[2025-08-01 06:24:34.831] [LOG]   All module helpers loaded. 
[2025-08-01 06:24:34.834] [LOG]   Starting server on port 8080 ...  
[2025-08-01 06:24:35.229] [ERROR] Whoops! There was an uncaught exception... 
[2025-08-01 06:24:35.233] [ERROR] Error: listen EADDRINUSE: address already in use ::1:8080
    at Server.setupListenHandle [as _listen2] (node:net:1940:16)
    at listenInCluster (node:net:1997:12)
    at GetAddrInfoReqWrap.callback (node:net:2206:7)
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:134:8) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::1',
  port: 8080
} 
[2025-08-01 06:24:35.234] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? 
[2025-08-01 06:24:35.234] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues 
[2025-08-01 06:24:35.591] [INFO]  System information:
### SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 5 Model B Rev 1.1; virtual: false
### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.34+rpt-rpi-2712
### VERSIONS: electron: 36.7.3; used node: 22.17.1; installed node: 22.17.1; npm: 10.9.2; pm2: 6.0.8
### OTHER:    timeZone: Australia/Melbourne; ELECTRON_ENABLE_GPU: undefined 

The config file is not changed at all. When I started getting a different port in use issue, I tried to find what else was using it, but I couldn’t find anything else.
I wasn’t too sure if running Raspberry Pi Connect was causing an issue.
I suspect I am just using this incorrectly. Once I resolve it, I can start making proper changes.

Thanks in advance!