CalenderEXT2 with google calendars no longer displaying

chris_d

I have an issue with CalendarEXT2.
It has been displaying fine for a good long while but at some time around early Jan it stops displaying at all, leaving just a gap on the screen where it was previously displaying.
As part of troubleshooting I upgraded to the latest version of Magic Mirror and then re-installed something called “request” which was referred to in the logs. This allowed magic mirror to start again, but the same “missing” calendar occurs.

Any clues on where I can look to work out more?

sdetweil

@chris_d u can look in the place where u start MagicMirror.

npm start
or if you use pm2, then

pm2 logs --lines=???

where ??? is some number , default is 15

the module prints errors if it has trouble w the calendar

BKeyport

@chris_d Google was going to change how to get calendars from them, if they’ve implemented the changes, it won’t work anymore. I had to switch a long time ago because they did that with the business accounts. You may have to switch calendar providers.

chris_d

@sdetweil
I did a full restart, clearing the logs first, and this is the output.

0|MagicMir | [1088:0109/162348.758626:ERROR:connection.cc(66)] X connection error received.
0|MagicMir | [1088:0109/162348.798329:ERROR:connection.cc(66)] X connection error received.
0|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
0|MagicMir | npm ERR! code ELIFECYCLE
0|MagicMir | npm ERR! errno 1
0|MagicMir | npm ERR! magicmirror@2.18.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
0|MagicMir | npm ERR! Exit status 1
0|MagicMir | npm ERR! 
0|MagicMir | npm ERR! Failed at the magicmirror@2.18.0 start script.
0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
0|MagicMir | 
0|MagicMir | npm ERR! A complete log of this run can be found in:
0|MagicMir | npm ERR!     /home/pi/.npm/_logs/2022-01-09T16_23_53_376Z-debug.log
0|MagicMir | [1045:0109/162522.174590:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMir | [1077:0109/162523.097334:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMir | [1097:0109/162523.801422:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

The behaviour that I’m seeing is that all other modules load ok, but the space previously occupied with the Calendar-EXT2 is just blank

sdetweil

@chris_d could u show more of the logs. this isn’t enough

BKeyport

@sdetweil I may be wrong, but I doubt it - I intentionally broke one of my calendars, and CX2 did not produce an error - just reported “0 scanned, 0 selected” on the calendar. I don’t think CX2 is gonna help with this.

Also, I looked through my code, and I’ve noticed that some of my shared calendars are indeed Google calendars, so I’m gonna retract that statement.

My advice is to double check the settings within Google itself.