TUMBLEWEED Boot Errors after latest Update

Hi all,

After applying the latest updates via “zypper dup” this morning, I found the following errors in my boot.log:

 SKIP ] Ordering cycle found, skipping LSB: AppArmor initialization
 SKIP ] Ordering cycle found, skipping LSB: Set default boot entry if called

“journalctl -b” gives me:

Device dev-disk-by\x2dpartlabel-primary.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/
Job apparmor.service/start deleted to break ordering cycle starting with sysinit.target/start
Job cycle.service/start deleted to break ordering cycle starting with sysinit.target/start

“apparmor_status” gives me:

apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

Anything else seems fine and these errors do not cause any trouble till now…

What to do?

Thank you:)

There’s a factory mailing list thread on this:
Apparmor fails to start on boot in Tumbleweed

There’s also an open bug report:
Bug 924830 Apparmor service fails to start on boot

My plan is to wait and see what develops. In the meantime, I’m not panicking. I’ll continue to use the system even without apparmor running.

Good to know that I am not the only one affected by this and I will also wait :wink:

Thanks for the quick response…