calendar fetch goes wrong and gpu process error

rotorax

@karsten13

here is the information:

[2024-07-22 07:54:19.741] [INFO] System information:

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; raspberry: [object Object]; virtual: false

OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+

VERSIONS: electron: 29.1.6; used node: 20.9.0; installed node: 21.7.3; npm: 10.5.0; pm2: 5.3.1

OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined

karsten13

@rotorax said in calendar fetch goes wrong and gpu process error:

after upgrading to the second community release

this should be MagicMirror v2.28.0 which ships with electron version v31.1.0

[2024-07-22 07:54:19.741] [INFO]  System information:
### SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; raspberry: [object Object]; virtual: false
### OS:       platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+
### VERSIONS: electron: 29.1.6; used node: 20.9.0; installed node: 21.7.3; npm: 10.5.0; pm2: 5.3.1
### OTHER:    timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined

but your logs tell us that you are using electron v29.1.6

So how did you update? It seems you didn’t run the npm ... command (see documentation how to upgrade).

The calendar error should be fixed with the newer electron version.

bugsounet

@karsten13 maybe it’s related with node v21.x

karsten13

@bugsounet said in calendar fetch goes wrong and gpu process error:

@karsten13 maybe it’s related with node v21.x

I think not because he is running with electron and so using node v20.9.0 at runtime

@rotorax I’m still interested if it works with the correct electron version v31.1.0

bugsounet

@karsten13 don’t forget: node_helper use node version installed on system ;)
and node v20.9.0 i used on module core
—> So: fetch calandar use node version installed on system (node v21.x)

we checked this on a github issue, 5-6 months ago

sdetweil

@bugsounet no… this is why we have the electron-rebuild problem…

in electron mode, we have the embedded node engine… (all the work is done from inside the electron binary)

		"start": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js",

and need electron rebuild to match the binary level

in server only mode we need the npm rebuild to get to match the node version binary level

		"server": "node ./serveronly",

use on-off, or gpio… different compiles if they are different

this is a good reason to keep the the nodejs versions in sync

make them not syncd and switch between full and server only and you will see the binary level error

took my brain a while to see this

karsten13

found the old discussion here

rotorax

l@karsten13

hi, im running now in the recommended electron and a newer node version

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; raspberry: [object Object]; virtual: false
OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+
VERSIONS: electron: 31.1.0; used node: 20.14.0; installed node: 22.5.1; npm: 10.8.2; pm2: 5.4.1
OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined

The MM now starts very fast and without rebooting the raspberry. I’ll keep you updated.
Thanks in advance :)

rotorax