Occasional AppArmor and SELinux warnings when upgrading

[Serophis]

After the following situation:

WiFi and USB problems with AppArmor 5

Hi, This is basically a duplicate of my mail list thread for visibility. After Tumbleweed update to snapshot 20260514, which has AppArmor 5 my WiFi stopped working. <error> [1778917266.6687] device (wlp9s0): Couldn't initialize supplicant interface: Failed to D-Bus activate wpa_supplicant service Also lsusb shows only error “unable to initialize usb spec”. Disabling AppArmor (sudo systemctl disable apparmor.service) and rebooting solves these issues, but kinda isn’t very good solution. A…

I followed this guide to migrate to SELinux:
https://en.opensuse.org/Portal:SELinux/Setup

And I haven’t removed any AppArmor packages since the above guide didn’t mention it and apparently the migration is still in progress so for all I know it could result in some unpredictable behavior. Anyway…

These warnings tend to show up whenever I upgrade these days.

Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
Use --subdomainfs to override.

--- WARNING: Non-default installation with no btrfs `/` detected. 
------          Migration will continue but in case of selinux-policy downgrade - manual intervention might be needed. 
------          `/var/lib/selinux` will be deleted one month after migration 
---
INFO: SELinux policy modules are stored in `/etc/selinux`.      
and `/var/lib/selinux` removed. No interaction needed.

Is it anything to worry about?

[dcurtisfra]

@Serophis:

You’re using SELinux – the AppArmor Zypp history entry –

# 2026-06-18 12:34:48 Ausgabe des Skripts %posttrans(apparmor-abstractions-5.0.1-1.1.noarch):
# Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
# Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
# Use --subdomainfs to override.
# ++ DISABLE_RESTART_ON_UPDATE=no
# ++ DISABLE_STOP_ON_REMOVAL=no
# 2026-06-18 12:34:48 Ausgabe des Skripts %posttrans(apparmor-profiles-5.0.1-1.1.noarch):
# Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
# Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
# Use --subdomainfs to override.
# ++ DISABLE_RESTART_ON_UPDATE=no
# ++ DISABLE_STOP_ON_REMOVAL=no

is irrelevant because, you should have disabled the systemd apparmor.service.

• I suspect that, for those Tumbleweed systems which do not have SELinux enabled, it is relevant …

---

The “Non-default installation” Zypp history entry –

# 2026-06-23 09:33:54 selinux-policy-targeted-20260618-1.1.noarch.rpm installed ok
# Additional rpm output:
# --- WARNING: Non-default installation with no btrfs `/` detected. ---
# ---          Migration will continue but in case of selinux-policy downgrade - manual intervention might be needed. ---
# ---          `/var/lib/selinux` will be deleted one month after migration ---
# INFO: SELinux policy modules are stored in `/etc/selinux`.
#       and `/var/lib/selinux` removed. No interaction needed.
#

is informational only –

• ‘/var/lib/selinux’ is empty and, it should be removed in a month or so despite the system not using Btrfs …
• The policies are now stored in ‘/etc/selinux’.

If, in a month or so, the directory ‘/var/lib/selinux’ is still present, I guess that, we’ll have to remove it manually …