Package: apparmor Version: 4.1.0-1+b1 Severity: important X-Debbugs-Cc: [email protected]
Dear Maintainer, recently, some profiles (not all) fail to load because they don't "confirm to protocol". Happens both during boot and on manual reload. Couldn't reliably track down specific lines of these files that might cause it. The upstream FAQ suggests that the userland tools might've been build against kernel headers that are newer than the kernel. This is a sid machine however, currently 6.17.9-deb14, so probably(?) not the issue. The version of apparmor_parser that is currently in Debian-stable shows the same problem. I'm not sure what kind of other info I can provide currently Thank you -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.17.9+deb14-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apparmor depends on: ii debconf [debconf-2.0] 1.5.91 ii libc6 2.42-4 apparmor recommends no packages. Versions of packages apparmor suggests: pn apparmor-profiles-extra <none> ii apparmor-utils 4.1.0-1 -- Configuration Files: /etc/apparmor.d/firefox changed [not included] /etc/apparmor.d/tunables/home changed [not included] -- debconf information excluded
