@sdetweil I can’t find it (I’ve reverted to previous anyway), but bullseye actually runs OMX with a couple of library fixes, if I recall right, just takes a symlink or two to match up the shared libraries.

pi0w does NOT work on new bullseye image, due to lack of working browser no electron for armv6l both Chrome and Firefox crash with segment fault (compiled for armv7l), pi0w DOES work on legacy (buster) image use my install script to get all the parts working node and npm have to be upgraded from the experimental release channel downlevel chromium-browser installed start mm in server mode, with chromium as ui I will keep this updated as we learn more

https://www.tomshardware.com/amp/news/raspberry-pi-releases-legacy-os seems problems caused reissue of updated buster

@DarkV ok, my script is the only one I know about and it uses git lets do this to get a new copy and use your config/modules… copy paste this section to a terminal window cd ~ # save MM folder mv MagicMirror MagicMirror.org # install new MM (reply N to screen saver/pm2 bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)" once MM is installed again lets make THIS new version look like the old copy/paste this # copy files cd ~ cp MagicMirror.org/config/config.js MagicMirror/config cp MagicMirror.org/css/custom.css MagicMirror/css cd MagicMirror/modules # save the new default module folder mv default .. cd .. # copy all the org modules cp -r -p ~/MagicMirror.org/modules . cd modules # remove the old default modules folder rm -rf default # move back the new default mv ../default . cd ~/MagicMirror now npm start should work

See https://www.raspberrypi.org/blog/new-raspberry-pi-os-release-december-2020/

the next release will upgrade electron and a bunch of other components, and the staging is starting now. so, any pulls of the develop branch will get the next electron update…

@sdetweil can you give me a screenshot where I find the solved-button? Edit: Sorry, first I had to mark the question as question. Than there was the solved button. Well, this is kind of hidden :-)

I use a samba share from a linux box to all my devices and systems… window, pi, mac. i have access to the share on my mac… BUT not if pm2 starts MM… I get access denied… if I stop the pm2 instance and then start MM with npm start it works fine… this is the MMM-ImagesPhotos module, with a soft link (ln -s) to the share from the module folder.

in 2.13 we changed over to the node-ical calendar parser to fix a bunch of problems, and add support for microsoft timezone names… we didn’t know if this would impact other calendar modules, as we left in the ical (ical.js) calendar parser. we intend to remove the ical parser on the next release…(Jan 1 approx)

in 2.13 we are fixing the calendar handling for multiple timezones and non IANA timezone names. but to do this we are switching the library we use from ical.js to node-ical. currently in the develop branch the ical.js library is removed… any non-default calendar modules using the ical library will fail… are there any? CalendarExt2 uses its own copy of ical.js MMM-MyCalendar uses vendor/ical (which is broken already in 2.12) 2.13 is coming next week… help

see https://forum.magicmirror.builders/topic/13669/new-test-calendar-ics-parser-available