Description of problem: I plugged in the usb printer and the problem presented itself; sorry I can't provide more technical detail than this. the computer asked me to input two commands, which follow, though it still would not send pages to the printer: [richard@localhost ~]$ sudo grep hp-config_usb_p /var/log/audit/audit.log | audit2allow -M mypol [sudo] password for richard: could not write output file: [Errno 13] Permission denied: 'mypol.te' [richard@localhost ~]$ sudo semodule -i mypol.pp SELinux is preventing /usr/bin/python2.7 from 'write' accesses on the file /var/log/hp/hplip_config_usb_printer.log. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that python2.7 should be allowed write access on the hplip_config_usb_printer.log 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 hp-config_usb_p /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:cupsd_t:s0-s0:c0.c1023 Target Context system_u:object_r:cupsd_log_t:s0 Target Objects /var/log/hp/hplip_config_usb_printer.log [ file ] Source hp-config_usb_p Source Path /usr/bin/python2.7 Port <Unknown> Host (removed) Source RPM Packages python-2.7.5-3.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-69.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 Alert Count 4 First Seen 2013-08-13 16:32:34 PDT Last Seen 2013-08-20 20:02:52 PDT Local ID 77554b77-1e71-4736-b6c1-3be846209335 Raw Audit Messages type=AVC msg=audit(1377054172.616:477): avc: denied { write } for pid=2952 comm="hp-config_usb_p" name="hplip_config_usb_printer.log" dev="dm-2" ino=1585197 scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:cupsd_log_t:s0 tclass=file type=SYSCALL msg=audit(1377054172.616:477): arch=x86_64 syscall=open success=no exit=EACCES a0=1ef0100 a1=241 a2=1b6 a3=0 items=0 ppid=1 pid=2952 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=hp-config_usb_p exe=/usr/bin/python2.7 subj=system_u:system_r:cupsd_t:s0-s0:c0.c1023 key=(null) Hash: hp-config_usb_p,cupsd_t,cupsd_log_t,file,write Additional info: reporter: libreport-2.1.6 hashmarkername: setroubleshoot kernel: 3.10.7-200.fc19.x86_64 type: libreport
Could hp-config_usb_p append own logs?
FWIW, we don't ship hp-config_usb_printer, so this AVC message comes from installing HPLIP from elsewhere.
Richard Do the audit2allow command while sitting in /tmp. I think for some reason root is not allowed to write in your homedir, Probably NFS?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.