I ran into this recently with something else. The pList was being modified at some time by another program.
I set up a process watcher on the file to detect when it was being changed and which process was changing it. If you need, I can send you the app I used to do that. > On Apr 19, 2025, at 4:53 AM, Gabriel Zachmann via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > >> >> The only thing I can think of is that, if legacyScreenSaver is still running >> an old instance of your screensaver (which you've learned can now happen), >> it is somehow caching the special screensaver defaults objects and values, >> so it doesn't read from disk the next time you invoke it. Here's what you >> should try: >> >> 1. Make sure legacyScreenSaver is not running in Activity Monitor. Quit/kill >> it if it is. >> 2. Open the System Prefs and change your screensaver's prefs. >> 3. Run it to see if the changes are kept. > > > I think that's it. > I tried your experiment and i think it proves that there are other instances > of my screensaver running. > > Is there an easy way to check, if other instances are still running? > > Best regards, Gabriel > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
