Description of problem: Whenever I connect my bluetooth headset with blueman, I get this error, then my headset disconnects. So I cannot currently connect my bluetooth headset. This might have to do with this: https://retrace.fedoraproject.org/faf/reports/925610/ SELinux is preventing python3 from 'execute' accesses on the file ldconfig. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that python3 should be allowed execute access on the ldconfig 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 'python3' --raw | audit2allow -M my-python3 # semodule -X 300 -i my-python3.pp Additional Information: Source Context system_u:system_r:blueman_t:s0-s0:c0.c1023 Target Context system_u:object_r:ldconfig_exec_t:s0 Target Objects ldconfig [ file ] Source python3 Source Path python3 Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-158.15.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.4.9-300.fc23.x86_64 #1 SMP Wed May 4 23:56:27 UTC 2016 x86_64 x86_64 Alert Count 5 First Seen 2016-05-23 16:17:41 CDT Last Seen 2016-05-23 16:21:22 CDT Local ID 9b22d4d5-86e2-45d3-89d2-e56983b28610 Raw Audit Messages type=AVC msg=audit(1464038482.6:341): avc: denied { execute } for pid=2472 comm="python3" name="ldconfig" dev="sda4" ino=2098081 scontext=system_u:system_r:blueman_t:s0-s0:c0.c1023 tcontext=system_u:object_r:ldconfig_exec_t:s0 tclass=file permissive=0 Hash: python3,blueman_t,ldconfig_exec_t,file,execute Version-Release number of selected component: selinux-policy-3.13.1-158.15.fc23.noarch Additional info: reporter: libreport-2.6.4 hashmarkername: setroubleshoot kernel: 4.4.9-300.fc23.x86_64 type: libreport
Why is this bug low severity? It appears to me blueman wants to exec ldconfig. Maybe searching for dynamic libraries. Perhaps allow it? I tried to allow manually with audit2allow and needed a couple more access types. Please see bug 1362544 that appears to me is the same issue but on Fedora 24.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.