Summary: SELinux is preventing gnome-session "add_name" access on 3593. Detailed Description: [SELinux is in permissive mode. This access was not denied.] SELinux denied access requested by gnome-session. It is not expected that this access is required by gnome-session 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://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:initrc_tmp_t:s0 Target Objects 3593 [ dir ] Source gnome-session Source Path gnome-session Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.6.32-99.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.33.1 #3 SMP PREEMPT Thu Mar 18 14:59:42 EDT 2010 i686 i686 Alert Count 1 First Seen Fri 19 Mar 2010 07:02:29 AM EDT Last Seen Fri 19 Mar 2010 07:02:29 AM EDT Local ID 53e50660-7708-4691-a7a9-beb0238b0113 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1268996549.287:9): avc: denied { add_name } for pid=3593 comm="gnome-session" name="3593" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=dir Hash String generated from catchall,gnome-session,xdm_t,initrc_tmp_t,dir,add_name audit2allow suggests: #============= xdm_t ============== allow xdm_t initrc_tmp_t:dir add_name;
I feel like I should really know what these are about, but I haven't gotten around to it yet. I'm actually getting multiple messages like this. I'm guessing it's something to do with my tmp directory? What would I have done to mess this up so that I can try to be more proactive?
Looks like this is a dup. *** This bug has been marked as a duplicate of bug 570306 ***