Hide Forgot
Description of problem: I was trying to connect with my Bluetooth headset using Gnome Settings. Headset connected for a second, then disconnected (it signalled disconnection). Gnome Settings then crashed. After few seconds SELinux notification appeared. It's the first time I use Fedora, so i have no idea if the problem was there before. SELinux is preventing dbus-daemon from read, write access on the socket socket. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that dbus-daemon should be allowed read write access on the socket 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-daemon' --raw | audit2allow -M my-dbusdaemon # semodule -X 300 -i my-dbusdaemon.pp Additional Information: Source Context system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 Target Context system_u:system_r:init_t:s0 Target Objects socket [ socket ] Source dbus-daemon Source Path dbus-daemon Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-283.14.fc27.noarch selinux- policy-3.13.1-283.32.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.13.9-300.fc27.x86_64 #1 SMP Mon Oct 23 13:41:58 UTC 2017 x86_64 x86_64 Alert Count 1 First Seen 2018-04-30 00:06:56 CEST Last Seen 2018-04-30 00:06:56 CEST Local ID bc21f912-13c8-44ad-9fc1-016aecaf95bd Raw Audit Messages type=AVC msg=audit(1525039616.925:910): avc: denied { read write } for pid=744 comm="dbus-daemon" path="socket:[828458]" dev="sockfs" ino=828458 scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:init_t:s0 tclass=socket permissive=0 Hash: dbus-daemon,system_dbusd_t,init_t,socket,read,write Version-Release number of selected component: selinux-policy-3.13.1-283.14.fc27.noarch selinux-policy-3.13.1-283.32.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport Potential duplicate: bug 1496247
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.