Hide Forgot
SELinux is preventing /usr/libexec/gdm-simple-slave from 'write' accesses on the sock_file log. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that gdm-simple-slave should be allowed write access on the log sock_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: # grep gdm-simple-slav /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:device_t:s0 Target Objects log [ sock_file ] Source gdm-simple-slav Source Path /usr/libexec/gdm-simple-slave Port <Unknown> Host (removed) Source RPM Packages gdm-2.91.94-1.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-6.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.1-6.fc15.x86_64 #1 SMP Wed Mar 23 22:43:31 UTC 2011 x86_64 x86_64 Alert Count 163 First Seen Fri 25 Mar 2011 08:52:20 AM CLST Last Seen Sun 27 Mar 2011 12:01:55 AM CLST Local ID 1d960aa6-c2e4-449b-afa8-5f5e05f6d4f4 Raw Audit Messages type=AVC msg=audit(1301194915.921:1039): avc: denied { write } for pid=1297 comm="gdm-simple-slav" name="log" dev=devtmpfs ino=16533 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=sock_file type=SYSCALL msg=audit(1301194915.921:1039): arch=x86_64 syscall=connect success=no exit=EACCES a0=c a1=330c1997c0 a2=6e a3=0 items=0 ppid=1269 pid=1297 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=gdm-simple-slav exe=/usr/libexec/gdm-simple-slave subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash: gdm-simple-slav,xdm_t,device_t,sock_file,write audit2allow #============= xdm_t ============== allow xdm_t device_t:sock_file write; audit2allow -R #============= xdm_t ============== allow xdm_t device_t:sock_file write;
*** This bug has been marked as a duplicate of bug 691145 ***