After upgrading Lulu, rules show empty - 2.6.2, multiple macOS versions

[justdayan]

upgraded Lulu to 2.6.2 on Catalina and Monterey.. Rules -> show, empty, all rules disappeared but are still in affect. However, I can disable or enable a single entity because I can't see it. I know the rules are there because I've migrated them via export/import and it tells me the number of rules imported, but shows me no rules. This means I can't disable/enable by rule.

[Noiden]

Same here but from 2.6.2 to 2.6.3, all rules are gone from "LuLu Rules" but still in affect.

I get this error in the Console when I start the "Rules" section in LuLu.

_ERROR: failed to execute daemon XPC method '-[XPCDaemonClient getRules]block_invoke' (error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named VBG97UB4TA.com.objective-see.lulu was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003." UserInfo={NSDebugDescription=The connection to service named VBG97UB4TA.com.objective-see.lulu was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003.})

[objective-see]

Hrmm, sorry about this!

Can you please:

1. check for any crash reports (via Console.app) ....an XPC invalidation is often a result of something crashing

2. Post your /Library/Objective-See/LuLu/rules.plist file here (or email [email protected])

3. Post any other relevant log messages from the log, which can be streamed from the Terminal via: log stream --level debug --predicate="subsystem='com.objective-see.lulu'"

[smktpd]

I had worse experience: I used brew to update lulu, it somehow screwed things up so that I had to do brew reinstall lulu and thus I actually lost all my rules, which sucks large, since Lulu has no export/import rules functionality 😢

[justdayan]

This is exactly what I experienced.. I couldn't migrate my rules, so I had to start from scratch on multiple machines.

On Fri, Mar 22, 2024 at 9:11 AM smktpd @.***> wrote:

I had worse experience: I used brew to update lulu, it somehow screwed things up so that I have to do brew reinstall lulu and thus I actually lost all my rules, which sucks large, since Lulu has no export/import rules functionality 😢

— Reply to this email directly, view it on GitHub https://github.com/objective-see/LuLu/issues/590#issuecomment-2015073626, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEKJHGIFXBT7N2I3TP5F7LYZQUY7AVCNFSM6AAAAABDVBD4YOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGA3TGNRSGY . You are receiving this because you authored the thread.Message ID: @.***>

[Noiden]

I choose to reinstall, to get a working rule list again. There is actually an export option in the systray icon "LuLu > Rules > Export..." Where it seems that you can export your rules to a json file.

It had been nice to automate that process.

Or is it possible to just take a backup of the "rules.plist" file and just restore that one after an upgrade? Or could that file be obsolete or not work with newer versions of LuLu?

@objective-see I'm sorry, I can't help anymore with logs and stuff because I already have reinstalled LuLu and now everything works fine.

[objective-see]

A few things worth noting:

1. Upgrading via brew won't work ...and will actually trigger a full uninstall (which will wipe any/all rules). LuLu uses a network (system) extension, which macOS, by design, makes very difficult for external programs/scripts to remove. LuLu's installer, is appropriately signed & entitled, and thus can programmatically remove/replace it during an upgrade. Brew sadly cannot :\

2. The brew recipe to install/upgrade LuLu is not created by @objective-see

3. During a normal upgrade (via LuLu's installer, not via brew), rules of course are preserved.

[Noiden]

A few things worth noting:

1. Upgrading via brew won't work ...and will actually trigger a full uninstall (which will wipe any/all rules). LuLu uses a network (system) extension, which macOS, by design, makes very difficult for external programs/scripts to remove. LuLu's installer, is appropriately signed & entitled, and thus can programmatically remove/replace it during an upgrade. Brew sadly cannot :\
2. The brew recipe to install/upgrade LuLu is not created by @objective-see
3. During a normal upgrade (via LuLu's installer, not via brew), rules of course are preserved.

Aha, thanks for the input, I think I had it installed through brew when this happend. Now I can't remember, but if I have it through brew this time also I should export the rules and uninstall the "brew edition" and install through the ordinary LuLu installer.

Thanks.

[kerim]

I just experienced this. Reinstalling fixed the issue.

[JANguaishen]

Hrmm, sorry about this!

Can you please:

1. check for any crash reports (via Console.app) ....an XPC invalidation is often a result of something crashing
2. Post your /Library/Objective-See/LuLu/rules.plist file here (or email [email protected])
3. Post any other relevant log messages from the log, which can be streamed from the Terminal via: log stream --level debug --predicate="subsystem='com.objective-see.lulu'"

How can I determine what error causes XPC invalidation? The program I developed myself also encountered such a problem. Or is there any way to reset it? Restarting the program doesn't work. Now, the only way is to restart the device for it to function properly.