Description of problem: This started after the latest upate and happens on every boot or reboot. SELinux is preventing /usr/lib/systemd/systemd-oomd from 'watch' accesses on the sock_file /run/dbus/system_bus_socket. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-oomd should be allowed watch access on the system_bus_socket sock_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'systemd-oomd' --raw | audit2allow -M my-systemdoomd # semodule -X 300 -i my-systemdoomd.pp Additional Information: Source Context system_u:system_r:systemd_oomd_t:s0 Target Context system_u:object_r:system_dbusd_var_run_t:s0 Target Objects /run/dbus/system_bus_socket [ sock_file ] Source systemd-oomd Source Path /usr/lib/systemd/systemd-oomd Port <Unknown> Host (removed) Source RPM Packages systemd-udev-257.7-1.fc42.x86_64 Target RPM Packages SELinux Policy RPM selinux-policy-targeted-42.2-1.fc42.noarch Local Policy RPM selinux-policy-targeted-42.2-1.fc42.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.15.8-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 24 13:26:52 UTC 2025 x86_64 Alert Count 2 First Seen 2025-07-25 07:27:12 BST Last Seen 2025-07-25 16:27:35 BST Local ID 2f62335b-c787-4212-b66a-27a176b32992 Raw Audit Messages type=AVC msg=audit(1753457255.13:63): avc: denied { watch } for pid=1130 comm="systemd-oomd" path="/run/dbus/system_bus_socket" dev="tmpfs" ino=2887 scontext=system_u:system_r:systemd_oomd_t:s0 tcontext=system_u:object_r:system_dbusd_var_run_t:s0 tclass=sock_file permissive=1 type=SYSCALL msg=audit(1753457255.13:63): arch=x86_64 syscall=inotify_add_watch success=yes exit=EINTR a0=7 a1=55f27828f660 a2=2000d84 a3=1 items=0 ppid=1 pid=1130 auid=4294967295 uid=999 gid=999 euid=999 suid=999 fsuid=999 egid=999 sgid=999 fsgid=999 tty=(none) ses=4294967295 comm=systemd-oomd exe=/usr/lib/systemd/systemd-oomd subj=system_u:system_r:systemd_oomd_t:s0 key=(null) Hash: systemd-oomd,systemd_oomd_t,system_dbusd_var_run_t,sock_file,watch Version-Release number of selected component: selinux-policy-targeted-42.2-1.fc42.noarch Additional info: reporter: libreport-2.17.15 package: selinux-policy-targeted-42.2-1.fc42.noarch kernel: 6.15.8-200.fc42.x86_64 component: selinux-policy reason: SELinux is preventing /usr/lib/systemd/systemd-oomd from 'watch' accesses on the sock_file /run/dbus/system_bus_socket. hashmarkername: setroubleshoot type: libreport comment: This started after the latest upate and happens on every boot or reboot. component: selinux-policy
Created attachment 2098235 [details] File: os_info
Created attachment 2098236 [details] File: description
*** Bug 2383766 has been marked as a duplicate of this bug. ***
*** Bug 2383648 has been marked as a duplicate of this bug. ***
*** Bug 2383703 has been marked as a duplicate of this bug. ***
*** Bug 2383761 has been marked as a duplicate of this bug. ***
FEDORA-2025-9665662503 (selinux-policy-42.3-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-9665662503
FEDORA-2025-9665662503 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-9665662503` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9665662503 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Fixes it for me, tested over a few days, reboots and cold starts. Thank you.
FEDORA-2025-9665662503 (selinux-policy-42.3-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.