https://bugzilla.novell.com/show_bug.cgi?id=854351 https://bugzilla.novell.com/show_bug.cgi?id=854351#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2013-12-07 23:48:40 CET --- Welcome back, Scott ;-) I know the status of the YaST AppArmor module is bad, but unfortunately there's not much I can do about it. The code is quite old and needs other old (and not really maintained) perl modules from AppArmor (which is switching to python for the tools like aa-logprof). The code that was used for notifications is unmaintained since years and incompatible with nowaday's log format. Even if I'd re-enable it, the only thing it would do is sending you an always-empty report. This sums up to: This is nothing that needs "some fixes" - the YaST module needs a full rewrite, and the time to do it. IIRC I already told you in your previous bugreport how to setup a cronjob as workaround. Maybe there's also some hope. I have a possible volunteer to rewrite the YaST module, but he seems to be quite busy, which means I can't give you any target date. If you want to get your hands dirty, I'm sure he'll welcome some help ;-) BTW: While I like your "expected result", it is sometimes hard to do it for various reasons. And I'm talking about lots of software, not only YaST. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.