Summary: SELinux is preventing /usr/bin/python "write" access on prnt. Detailed Description: SELinux denied access requested by python. It is not expected that this access is required by python 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:hplip_t:s0-s0:c0.c1023 Target Context system_u:object_r:usr_t:s0 Target Objects prnt [ dir ] Source python Source Path /usr/bin/python Port <Unknown> Host (removed) Source RPM Packages python-2.6.2-2.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-162.fc12.i686 #1 SMP Fri Dec 4 01:09:09 EST 2009 i686 i686 Alert Count 8 First Seen Wed 09 Dec 2009 12:48:12 AM BRST Last Seen Wed 09 Dec 2009 12:48:33 AM BRST Local ID a8bedbdf-3073-41d0-9779-99d88d2434d5 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1260326913.553:94): avc: denied { write } for pid=17780 comm="python" name="prnt" dev=sda1 ino=139323 scontext=system_u:system_r:hplip_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir node=(removed) type=SYSCALL msg=audit(1260326913.553:94): arch=40000003 syscall=10 success=no exit=-13 a0=bff8b35b a1=b742e3b0 a2=603a868 a3=bff8c3bb items=0 ppid=17774 pid=17780 auid=4294967295 uid=0 gid=7 euid=0 suid=0 fsuid=0 egid=7 sgid=7 fsgid=7 tty=(none) ses=4294967295 comm="python" exe="/usr/bin/python" subj=system_u:system_r:hplip_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-55.fc12,catchall,python,hplip_t,usr_t,dir,write audit2allow suggests: #============= hplip_t ============== allow hplip_t usr_t:dir write;
*** This bug has been marked as a duplicate of bug 538441 ***