Hello, Short version: Can someone please check the YaST2 AppArmor module if something needs to be changed for the aa-logprof and aa-genprof change described below? Long version: I'm currently working on a little feature in aa-logprof and aa-genprof to enable logging of all json input and output, which might make debugging a bit easier, and might also make it possible to easily create tests for a complete aa-logprof run. (YaST will be helpful to create these tests, since it's currently the only json client for aa-logprof.) The json format itsself will not change, however I'll have to switch to json mode a bit later. You'll only notice this if there's an error on startup, for example a broken config file or missing apparmor_parser. Now: # aa-logprof --json {"dialog": "apparmor-json-version","data": "2.12"} ERROR: Can't find apparmor_parser at /sbin/apparmor_parser After the change: # python3 aa-logprof --json ERROR: Can't find apparmor_parser at /sbin/apparmor_parser Note that the {"dialog": ... } line no longer gets printed if aa- logprof or aa-genprof error out on startup. For completeness: ERROR: gets printed on stderr, and $? = 1. Again: If there is no error on startup, nothing will change. Is this change a problem for the YaST AppArmor module? (I'd offer to update the json version, but since it no longer gets printed on startup errors, I'm not sure if that's too helpful ;-) So far, this change only exists as a MR: https://gitlab.com/apparmor/apparmor/-/merge_requests/1078 It will probably be included in AppArmor 4.0 (to be released in some months). Regards, Christian Boltz -- "Guten Tag, ich möchte gerne einen Tisch reservieren." "Gerne, auf welchen Namen denn?" "31337 /-/ /\ X0R!" [Jens Benecke in suse-linux zum Thema Realnames]