yes, thanks.
We had similar errors with older electron versions running with node v18, but you are using the newest mm release.
yes, thanks.
We had similar errors with older electron versions running with node v18, but you are using the newest mm release.
please provide information about your mm-version and node/electron versions.
You find them in the logs, example:
[2024-10-03 23:10:32.636] [LOG] Starting MagicMirror: v2.30.0-develop
...
[2024-10-03 23:10:33.352] [INFO] System information:
### SYSTEM: manufacturer: Microsoft; model: Docker Container; virtual: true
### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: x64; kernel: 5.15.153.1-microsoft-standard-WSL2
### VERSIONS: electron: undefined; used node: 22.9.0; installed node: 22.9.0; npm: 10.8.3; pm2:
### OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined
this is a “feature” of nodebb since release v3.9.1, nothing we can do.
https://github.com/MagicMirrorOrg/MagicMirror/releases/tag/v2.29.0
Thanks to: @bugsounet, @dkallen78, @jargordon, @khassel, @KristjanESPERANTO, @MarcLandis, @rejas, @ryan-d-williams, @sdetweil, @skpanagiotis.
⚠️ This release needs nodejs version
v20
orv22
, minimum version isv20.9.0
npm run test:spelling
and handle spelling issues (#3544)config.paths.vendor
(could not work because vendor
is hardcoded in index.html
), renamed config.paths.modules
to config.foreignModulesDir
, added variable MM_CUSTOMCSS_FILE
which - if set - overrides config.customCss
, added variable MM_MODULES_DIR
which - if set - overrides config.foreignModulesDir
, added test for MM_MODULES_DIR
(#3530)index.html
when loading script or stylesheet files failsMODULE_DOM_UPDATED
notification each time the DOM is re-rendered via updateDom
(#3534)node-libgpiod
library to electron-rebuild tests (#3563)eslint-plugin-import
, because it doesn’t support ESLint v9. We will reenter it later when it does.onoff
library from electron-rebuild tests (#3563)apiVersion
default from 2.5 to 3.0 (#3424)node-ical
version to 0.18.0
with exception allow-ghsas: GHSA-8hc4-vh64-cxmj
in dep-review.yaml
(which should removed after next node-ical
update)config_check.js
package.json
(currently v20.9.0) (#3559) and except for v21 (no security updates) (#3561)eslint-plugin-unicorn
by @eslint/js
checks
badge in README.mdjs/positions.js
when linting (this file is created at runtime)the package.json
contains "webuntis": "latest"
so it will always install the latest version of this dependency.
I suspect that there were breaking changes within some versions, you could try an older version (see https://github.com/SchoolUtils/WebUntis/tags).
You have to update package.json
with e.g. "webuntis": "2.2.1"
and execute npm install
in the module folder.
can you provide the logs of system information?
Something like this:
[2024-09-19 21:52:27.750] [INFO] System information:
### SYSTEM: manufacturer: Microsoft; model: Docker Container; virtual: true
### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: x64; kernel: 5.15.153.1-microsoft-standard-WSL2
### VERSIONS: electron: undefined; used node: 22.9.0; installed node: 22.9.0; npm: 10.8.3; pm2:
### OTHER: timeZone: UTC; ELECTRON_ENABLE_GPU: undefined
I won’t stop you from opening an issue …
@sdetweil said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:
@stephanvdplas i understand, looks like something changed in 31, which can be a bug as well.
you’ve got a workaround in the near term.
id open an issue on the MagicMirror github page with the error and a link to this topic so we don’t lose it.
finding a test environment will be the tough thing
no, we don’t need another issue we cannot solve.
The problem is chromium which is becoming stricter with every release and with every new electron version you get a new chromium version:
electron Chromium
31.4.0 126.0.6478.23
31.3.1 126.0.6478.185
31.3.0 126.0.6478.183
31.2.0 126.0.6478.127
31.1.0 126.0.6478.114
31.0.2 126.0.6478.61
31.0.0 126.0.6445.0
30.1.0 124.0.6367.243
30.0.9 124.0.6367.233
30.0.8 124.0.6367.230
30.0.7 124.0.6367.221
30.0.5 124.0.6367.207
30.0.4 124.0.6367.201
30.0.3 124.0.6367.119
30.0.2 124.0.6367.91
30.0.1 124.0.6367.60
30.0.0 124.0.6323.0
Maybe related to this changed in Chromium 125.
We have to deal with this and downgrading chromium (indirect by downgrading electron) is no real solution.
@stephanvdplas said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:
I am quite sure about having the config right
sorry, my point is you have to google the error with the keyword “electron” and check if you find something which you can test