Package: dbus-broker Version: 33-1 Severity: normal Usertags: warnings I noticed that during boot the Linux kernel version 6.4.4 complains about how dbus-broker-launch uses memfd_create, it should use one of the MFD_EXEC nor MFD_NOEXEC_SEAL options. No reason is given though.
Aug 07 08:27:15 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus... Aug 07 08:27:15 dbus-broker-launch[756]: Kernel is missing AppArmor DBus support. Ignoring. Aug 07 08:27:15 systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Aug 07 08:27:15 systemd[1]: Reached target basic.target - Basic System. Aug 07 08:27:15 dbus-broker-launch[756]: Ready Aug 07 08:27:15 kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=756 'dbus-broker-lau' Aug 07 08:27:15 systemd[1]: Starting NetworkManager.service - Network Manager... -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dbus-broker depends on: ii dbus-system-bus-common 1.14.8-2 ii init-system-helpers 1.65.2 ii libapparmor1 3.0.8-3 ii libaudit1 1:3.1.1-1 ii libc6 2.37-6 ii libcap-ng0 0.8.3-1+b3 ii libexpat1 2.5.0-2 ii libselinux1 3.5-1 ii libsystemd0 254-1 ii systemd-sysv 254-1 Versions of packages dbus-broker recommends: ii dbus-bin 1.14.8-2 dbus-broker suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
