Problem installing new module (beginner), CalendarEXT3 not displaying

Manino

@MMRIZE this one is from an all brand new installation of the MM and EXT3. I did end the installation with the ”npm install”. Copy paste your config into mine and got this. I’am clearly doing something wrong but I can’t undestand what to do different.

MMRIZE

@Manino
Let’s test things.

Remove all other modules except calendar and MMM-CalendarExt3 then run again.
1-1) If no issue; Some of other modules might make interference.
1-2) Still happens; Run MM as dev mode (npm run start:dev) => This will show front-end dev console and there might be some useful console log. (or you can populate dev-console on MM with Ctrl+Shift+i or equivalent shortcut keys by your system)
Just in case, the first rendering takes time so wait a while after running it.

Manino

@MMRIZE Can you see something? I takes time for my posts to be accepted but now I have an all band new installation of the MM and the EXT3.

I did comment out(?) all the default models except the calendar. Correct? Still got the same view as above (my latest post), except the clock and date.

manino@raspberrypi:~ $ cd MagicMirror
manino@raspberrypi:~/MagicMirror $ npm run start:dev

magicmirror@2.24.0 start:dev
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js dev

[22.09.2023 09:26.03.030] [LOG] Starting MagicMirror: v2.24.0
[22.09.2023 09:26.03.044] [LOG] Loading config …
[22.09.2023 09:26.03.053] [DEBUG] config template file not exists, no envsubst
[22.09.2023 09:26.03.067] [LOG] Loading module helpers …
[22.09.2023 09:26.03.070] [LOG] No helper found for module: MMM-CalendarExt3.
[22.09.2023 09:26.03.620] [LOG] Initializing new module helper …
[22.09.2023 09:26.03.621] [LOG] Module helper loaded: calendar
[22.09.2023 09:26.03.622] [LOG] All module helpers loaded.
[22.09.2023 09:26.03.640] [LOG] Starting server on port 8080 …
[22.09.2023 09:26.04.084] [ERROR] Whoops! There was an uncaught exception…
[22.09.2023 09:26.04.097] [ERROR] Error: listen EADDRINUSE: address already in use ::1:8080
at Server.setupListenHandle [as _listen2] (node:net:1740:16)
at listenInCluster (node:net:1788:12)
at GetAddrInfoReqWrap.doListen [as callback] (node:net:1937:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:110:8) {
code: ‘EADDRINUSE’,
errno: -98,
syscall: ‘listen’,
address: ‘::1’,
port: 8080
}
[22.09.2023 09:26.04.098] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[22.09.2023 09:26.04.098] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information

MMRIZE

@Manino
You need to stop “pm2” first before try dev mode. This error means just you are executing mm twice(one from pm2 and one from npm run start:dev). That error is not related with your original issue.

sdetweil

@MMRIZE @Manino do

pm2 stop all

then u can do

npm start 
(ctrl-c to stop)

to test

Manino

@MMRIZE @sdetweil Oh, tnx! This is what I got. Have no idea if this is correct either. Thanks for your patience.

manino@raspberrypi:~ $ cd MagicMirror
manino@raspberrypi:~/MagicMirror $ pm2 stop all
[PM2] Applying action stopProcessId on app [all](ids: [ 0 ])
[PM2] [MagicMirror](0) ✓
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ MagicMirror        │ fork     │ 0    │ stopped   │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
manino@raspberrypi:~/MagicMirror $ npm start

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

[22.09.2023 21:59.20.958] [LOG]   Starting MagicMirror: v2.24.0
[22.09.2023 21:59.20.971] [LOG]   Loading config ...
[22.09.2023 21:59.20.980] [DEBUG] config template file not exists, no envsubst
[22.09.2023 21:59.20.989] [LOG]   Loading module helpers ...
[22.09.2023 21:59.20.997] [LOG]   No helper found for module: MMM-CalendarExt3.
[22.09.2023 21:59.21.413] [LOG]   Initializing new module helper ...
[22.09.2023 21:59.21.414] [LOG]   Module helper loaded: calendar
[22.09.2023 21:59.21.415] [LOG]   All module helpers loaded.
[22.09.2023 21:59.21.436] [LOG]   Starting server on port 8080 ... 
[22.09.2023 21:59.21.866] [LOG]   Server started ...
[22.09.2023 21:59.21.869] [LOG]   Connecting socket for: calendar
[22.09.2023 21:59.21.870] [LOG]   Starting node helper for: calendar
[22.09.2023 21:59.21.872] [LOG]   Sockets connected & modules started ...
[22.09.2023 21:59.21.950] [LOG]   Launching application.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
../../buildtools/third_party/libc++/trunk/include/vector:1471: assertion __n < size() failed: vector[] index out of bounds[1602:0922/215923.760165:ERROR:gpu_process_host.cc(954)] GPU process exited unexpectedly: exit_code=6
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
../../buildtools/third_party/libc++/trunk/include/vector:1471: assertion __n < size() failed: vector[] index out of bounds[1602:0922/215924.743937:ERROR:gpu_process_host.cc(954)] GPU process exited unexpectedly: exit_code=6
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
../../buildtools/third_party/libc++/trunk/include/vector:1471: assertion __n < size() failed: vector[] index out of bounds[1602:0922/215925.960665:ERROR:gpu_process_host.cc(954)] GPU process exited unexpectedly: exit_code=6
[22.09.2023 21:59.25.999] [LOG]   Create new calendarfetcher for url: https://ics.calendarlabs.com/709/45a0bb64/Fun_Holidays.ics - Interval: 3600000
[22.09.2023 21:59.26.871] [INFO]  Calendar-Fetcher: Broadcasting 59 events.
[1645:0922/215926.898550:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
^C/home/manino/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT

sdetweil

@Manino

‘/home/manino/package.json’

you are not in the MagicMirror folder

cd MagicMirror

sdetweil

@Manino do this

export ELECTRON_DISABLE_GPU=1
npm start

if that works, the add

export ELECTRON_DISABLE_GPU=1

in the ~/MagicMirror/installers/mm.sh

on a new line before the line with npm start

Manino

@sdetweil @MMRIZE Sry did post before writing all text…

I did try your thing @sdetweil but I could’nt get it right. Then I did the Install of the MM for 15 times or something, try different installation every time, change language and tested everything, and then one time I try this extra thing below. I am sure iv’e tried it before but that time it did’nt work. I don’t know why but now I have it.

Every time I do the installation of the MM (after imager), I do got an error in the text. But the MM start running anyway. Maybe that’s the problem?

Anyway this thing did work:
“When some submodule seems not installed and updated properly, try this.”
cd ~/MagicMirror/modules/MMM-CalendarExt3
git submodule update --init --recursive

sdetweil

@Manino the question is, WHY did it not get installed properly…

the install instructions

npm install

in the module folder SHOULD have done the work already…