Screen saver broken in Monterey

I have nearly 100k photos, I LOVE how the screensaver randomly brings back memories from my life, journeys, and adventures.

Same problem here.

15k+ photos.

Screensaver not working on my imac 2017

nor on my brand new macbook pro received yesterday (didn't migrate but just copy over my Photos Library).

Still doesn't work for me after upgrading to 12.2. All of my photos are on the cloud.

I am also having this screen saver issue...on my new MacBook Pro with Monterey 12.0.1 the Ken Burns screen saver is blank as are several others. How do I fix this?

Same, screen-saver issue but also all the default sources for setting the Classic screen saver (or any slideshow screen saver basically) is gone since Monterey.

12.2.1 didn't solve it either.

I don't think its on any priority list; Mac user since 1988; it's a different world now.

Thanks for the tip, tried it!

Unfortunately, the issue remained in Safe Mode, the Default collections as source are gone:(

Also not working on my iMac, but is working on my early 2015 MacBookPro13.

After many (many dozen) attempts using the official Apple instructions, I got it right, but there is no way I can tell you, I hope to never have to do it again!

Going to add some observations and confirm Classic and Ken Burns screen saver issues with Monterey, with zilch rendering as most everyone on this thread. It consistently does not render on the Main Display.

First the host is Mac mini (2018) running the 3 GHz 6-Core Intel Core i5. I also use eGPU (AMD Radeon RX 5700 XT 8 GB) to drive multimonitor setup given the long-outstanding issue wherein mini lacks stability in a triple monitor arrangement (when one monitor must use the HDMI port).

The 'Monterey' and highly touted 'hello' screen saver work fine, providing some degree of confidence that the neither Intel nor eGPU lack core OS drivers. Notwithstanding, the latter "script" lacks the traditional Apple finess: it does not complete all 'scripting' on the different display geometries prior to refresh. My opinion, ymmv

Now here is a "kicker": prior to choosing either of Classic or Ken Burns screen savers, setup wifi and connect iPad/iPhone as your sidekick. While all main screens remain blank, the screen saver will render on the sidekick display while in the 'separate display' mode as an extended display. The other screen saver types like floating, flip-up, sliding panels, shifting tiles, photo mobile perform similarly.

Since i have two "extended displays" in addition to the sidekick, I want to note that "Origami" and "Vintage Prints" would initialize the rendering on one or both extended displays, while only actively working on the sidekick. As one of our fellow sufferers noted, a low brightness rendition on a non-sidekick extended display did occur during my testing. This ultimately points to a failure in gamut processing routines, so a failed regression testing of the Quartz context (or whatever its called these days in the march to convergence with mobile by Cupertino) rewrites.

I check verified the display ColorSync ICC profiles on Monterey, and no repairs were indicated.

flatfootfloozy wrote:

The photo display screensaver options do not, in fact, display any jpeg png or jpg.

That is weird. Nearly all of the image files in the folder I have selected for my screensaver are PNG files and it's working as expected. I am using the Classic module.

Edit to add: I am using a folder of PNG and JPG/JPEG image files on my hard drive, not a folder from Photos. In case that makes a difference.

Not for me. I'm on 12.1 on a MBP 16 Max and no joy with screen saver. Previews alright, then goes back to a horrendous bright green when the saver actually kicks in. Update: After reading an earlier suggestion to rename the folder to Photos, it works. Haha. Great. Too bad we can't use whatever name we want, but at least that is a useful workaround. To clarify, I had a folder ~/Library/Screen Savers/Black and had to rename it to ~/Library/Screen Savers/Photos for it to work. It contains a black jpg only.

Upgraded to 12.1. Works now. Good job community.