http://bugzilla.opensuse.org/show_bug.cgi?id=881762 --- Comment #13 from Christian Boltz --- Can you test with older versions of the AppArmor perl modules? IMHO it's unlikely that it broke in the AppArmor perl modules, but checking it can't hurt ;-) and in case I'm wrong, we know what causes this bug ;-) Using a bzr checkout ("bzr checkout lp:apparmor", then "bzr up -r1234" with various revision numbers [1]) is probably the easiest way to test this - replace the perl modules in /usr/lib/perl5/vendor_perl/5.20.1/Immunix/ with an older revision and check if you can still reproduce this bug. [1] to get a list of revisions with changes in the perl modules, run bzr log deprecated/utils/Immunix/ |grep '^revno\|timestamp' FYI: the perl modules lived in utils/Immunix in earlier revisions. BTW: older versions of the perl modules don't understand dbus etc. rules, so you'll probably need to temporarily uninstall apparmor-profiles and apparmor-abstractions, and install apparmor-profiles 2.8.x instead. That all said - the only solution that is really maintainable on the long run is to rewrite the YaST module so that it works with the python code we now use. Needless to say that this isn't a small task ;-) A final question - do you really need YaST to edit your profiles? (This is a serious question - for me, editing with vi is much easier than clicking around in YaST, but OTOH I'm definitively not what you'd call "average user" ;-) -- You are receiving this mail because: You are on the CC list for the bug.