Ventura 13.1 first beta

Question

BernardTeo OP

Created Oct ’22

Replies 8

Boosts 1

Views 1.9k

Participants 6

All launchdaemons inside /Library/LaunchDaemons won't launch on reboot.

The launchdaemon plists seem to still work if you launch them manually with launchctl load -w but they don't survive a reboot.

It was still OK with Ventura 13.0 but something seems to have changed at the system level with 13.1. I've tried every variation with configuring the plists but nothing works.

There is a new SMAppService API with Ventura 13 betas but it's still too new - the old system needs to work until we've safely migrated to the new system.

Changing horses in midstream and drowning...

Does anyone else see this?

Boost

Answer 1

pandabeta OP

Nov ’22

We have exactly the same problem :( In Console.app, do you see any crash of sh related to your .plist?

0

Answer 2

BernardTeo OP

Nov ’22

I don't see anything related to any of the LaunchDaemons in the /Library/LaunchDaemons folder in the Console log. My feeling is that they may not even be launched, or no attempts have been made by the system to launch them on reboot, it seems.

0

Answer 3

BernardTeo OP

Nov ’22

A correction. Further observations. Plists that launch Privileged Helpers do get launched. Also, plists that launch periodic jobs appear to get launched. But plists that launch "Run At Load" executables are either not launched or there is some sort of a crash but I don't see any trace in the Console log.

0

Answer 4

frankfenn OP

Nov ’22

We are seeing the same problem, only 1 of our 2 launch daemons is being started. One item is missing from the Background Application list in system settings and for the rest it's saying: It's from an unknown developer even with our correct production signing.

0

Answer 5

BernardTeo OP

Nov ’22

This seems to have been solved in 13.1 beta 2, thankfully. Can now move on to more useful work. But hope it won't break again, in subsequent updates.

0

Answer 6

pandabeta OP

Dec ’22

We are seeing the same behavior in macOS 13.1 RC (22C65). Are you experiencing the same with this Release Candidate?

0

Answer 7

trinhtran OP

Mar ’23

Hi,

In my case, it works fine if my daemon is toggled on in Login Items. Otherwise, if it's off, it won't be launched on the next reboot. Now, I don't know how to ensure that Privileged Helpers get launched even when they're toggled off?

0

Answer 8

Serhio1990 OP

May ’23

Hello! We are experiencing this issue right now on 13.3.1 - daemons still don't launch on a reboot. Can anyone confirm that this issue still exists please. I had a daemon /Libary/LaunchDaemons + /Library/PrivilegedHelperTools

added AssociatedBundleIdentifiers - no luck
moved the daemon executable into the client bundle - no luck

...

well, frankly, i'm out of ideas...

0