Hello, [ I have a nomail subscription here, so please CC me if you reply ] FYI: the AppArmor update that is available for 42.1 and 42.2 since two days causes trouble - AppArmor won't be started on boot anymore :-( I'm still searching for the exact cause [1] - if you are interested in the details, please follow https://bugzilla.opensuse.org/show_bug.cgi?id=1017260 Workaround: systemctl enable apparmor.service systemctl reload apparmor.service Please also check if some running services run without their AppArmor profile. You can see this in aa-status in the section "... processes are unconfined but have a profile defined". Please restart any services listed there, or simply reboot. If someone has an idea how to fix this on the packaging level, please tell me ;-) Regards, Christian Boltz [1] It probably has to do with (re)adding the missing apparmor.service to the package - but I have no idea why the presets don't automatically enable apparmor.service. --

Surely SUSE need to also get SLED 12 working on hardware that new? I'd like to avoid to answer this question, next please! :) [> Richard Brown and Takashi Iwai in opensuse-factory]

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org