further errors

British_Kiwi

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!!
:)

British_Kiwi

@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

@British_Kiwi I think that error is due to the GPU being disabled by default

If the os has it enable in boot/config.txt
Then you can try

export ELECTRON_ENABLE_GPU=1
Then
npm start

If that works you can update the script used by pm2

British_Kiwi

@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

@British_Kiwi you have to be in the MagicMirror folder before npm start, right?

British_Kiwi