Description of problem: My Bluetooth earbuds do not connect if I have selinux enabled. Setting it to permissive allows it. The oddity was that I wasn't seeing any selinux logged error until I did: semodule -DB That, allowed me to get the report and suggested attached to this notification. I think this is a bug SELinux is preventing dbus-broker from read, write access on the bluetooth_socket bluetooth_socket. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that dbus-broker should be allowed read write access on the bluetooth_socket bluetooth_socket 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 'dbus-broker' --raw | audit2allow -M my-dbusbroker # semodule -X 300 -i my-dbusbroker.pp Additional Information: Source Context system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 Target Context system_u:system_r:unconfined_service_t:s0 Target Objects bluetooth_socket [ bluetooth_socket ] Source dbus-broker Source Path dbus-broker Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-minimum-40.17-1.fc40.noarch Local Policy RPM selinux-policy-minimum-40.17-1.fc40.noarch Selinux Enabled True Policy Type minimum Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.8.8-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Apr 27 17:53:31 UTC 2024 x86_64 Alert Count 2 First Seen 2024-05-06 10:58:12 CEST Last Seen 2024-05-06 10:59:40 CEST Local ID 99de2076-0e45-4c1b-b634-4e2bc8cc671f Raw Audit Messages type=AVC msg=audit(1714985980.394:359): avc: denied { read write } for pid=3178 comm="dbus-broker" path="socket:[181898]" dev="sockfs" ino=181898 scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=bluetooth_socket permissive=0 Hash: dbus-broker,system_dbusd_t,unconfined_service_t,bluetooth_socket,read,write Version-Release number of selected component: selinux-policy-minimum-40.17-1.fc40.noarch Additional info: reporter: libreport-2.17.15 reason: SELinux is preventing dbus-broker from read, write access on the bluetooth_socket bluetooth_socket. package: selinux-policy-minimum-40.17-1.fc40.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.8.8-300.fc40.x86_64 component: selinux-policy
Created attachment 2031583 [details] File: description
Created attachment 2031584 [details] File: os_info
Paolo, dbus wants to IPC to some service, do you know which one? ps -eo pid,ppid,fname,cmd,context | grep -e CONTEXT -e unconfined_service_t
Are you still seeing this? The AVC is similar to the ones in Bug 2331485 and Bug 2329684.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.