Description of problem: I don't think abrt needs to read group file, connect or write to nscd socket Thanks SELinux is preventing abrt-dump-xorg from 'connectto' accesses on the unix_stream_socket /run/nscd/socket. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that abrt-dump-xorg should be allowed connectto access on the socket unix_stream_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: # grep abrt-dump-xorg /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:abrt_dump_oops_t:s0 Target Context system_u:system_r:nscd_t:s0 Target Objects /run/nscd/socket [ unix_stream_socket ] Source abrt-dump-xorg Source Path abrt-dump-xorg Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages nscd-2.21-7.fc22.x86_64 Policy RPM selinux-policy-3.13.1-128.8.fc22.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.1.4-200.fc22.x86_64 #1 SMP Tue Aug 4 03:22:33 UTC 2015 x86_64 x86_64 Alert Count 28 First Seen 2015-08-05 14:49:14 IST Last Seen 2015-08-15 15:48:38 IST Local ID 434fb679-7689-4f9b-a179-349ca14d2e13 Raw Audit Messages type=AVC msg=audit(1439633918.598:590): avc: denied { connectto } for pid=670 comm="abrt-dump-journ" path="/run/nscd/socket" scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:system_r:nscd_t:s0 tclass=unix_stream_socket permissive=1 Hash: abrt-dump-xorg,abrt_dump_oops_t,nscd_t,unix_stream_socket,connectto Version-Release number of selected component: selinux-policy-3.13.1-128.8.fc22.noarch Additional info: reporter: libreport-2.6.2 hashmarkername: setroubleshoot kernel: 4.1.4-200.fc22.x86_64 type: libreport
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.