@Stuart_P wrote:Installing the app directly from the script has a
different outcome to installing it from the re-packaged custom
packageYou put that perfectly, because I have the same workflow and am
running into the same problem. I'll give your sugg...
Urgh, I really hope that's not the case.The screen burn-in thing is
definitely a concern, especially in our labs where we have Wacom Cintiqs
or even Apple Studio Displays.I've never been able to get loginwindow
screensavers working ever since the log...
Also interestingly, when the screen saver fails to start on the login
window, there is a unified log entry that says:2023-07-26
12:51:40.069753-0700 0x77722 Error 0x0 20299 0 lwsslauncher:
(LaunchServices) [com.apple.launchservices:open] LAUNCH: requ...
Yup, that's exactly how I did it. The profile is signed and everything
so that it doesn't get changed by Jamf.For testing, I set
loginWindowIdleTime to 5, just so I can tell quickly whether it works or
not. But no longer how long I leave it at the lo...
Boy, I must really be missing something obvious. I've been trying to get
a loginwindow screensaver working for ages and have never had luck. If
it's verified to be working in Ventura, I must be overlooking something.
I know that Jamf's built-in Scree...
