Summary: SELinux is preventing /usr/sbin/abrtd "module_request" access. Detailed Description: SELinux denied access requested by abrtd. It is not expected that this access is required by abrtd and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:system_r:kernel_t:s0 Target Objects None [ system ] Source abrtd Source Path /usr/sbin/abrtd Port <Unknown> Host (removed) Source RPM Packages abrt-1.0.0-1.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-55.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.6-166.fc12.i686 #1 SMP Wed Dec 9 11:14:59 EST 2009 i686 i686 Alert Count 1 First Seen Mon 14 Dec 2009 08:20:50 PM EET Last Seen Mon 14 Dec 2009 08:20:50 PM EET Local ID 843f535a-c151-4ff7-8551-5afdca4c509e Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1260814850.488:132): avc: denied { module_request } for pid=1382 comm="abrtd" scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:kernel_t:s0 tclass=system node=(removed) type=SYSCALL msg=audit(1260814850.488:132): arch=40000003 syscall=102 success=no exit=-97 a0=1 a1=bfcdd800 a2=b82f80 a3=94544a8 items=0 ppid=1 pid=1382 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="abrtd" exe="/usr/sbin/abrtd" subj=system_u:system_r:abrt_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-55.fc12,catchall,abrtd,abrt_t,kernel_t,system,module_request audit2allow suggests: #============= abrt_t ============== allow abrt_t kernel_t:system module_request;
*** This bug has been marked as a duplicate of bug 527936 ***