Bug 559945

Summary: SELinux is preventing /usr/bin/python "write" access on prnt.
Product: [Fedora] Fedora Reporter: Ingimar Jonsson <ingimar>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: Belletz_89, bryandeering6775, dwalsh, eduardo.marcelo.palacios, flbrasov, ingimar, joshgreinke123, kkshethin, mgrepl, pgschroeder, rnorris1
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:bd0cfc47439ba542992785a540576e3ec4435dcf6af632b8fcfabef9c3801b72
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-29 13:50:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ingimar Jonsson 2010-01-29 12:37:37 UTC 
Hash String generated from  selinux-policy-3.6.32-78.fc12,catchall,python,hplip_t,usr_t,dir,write
audit2allow suggests:
Comment 1 Daniel Walsh 2010-01-29 13:50:44 UTC 

*** This bug has been marked as a duplicate of bug 516078 ***
Comment 2 Philip Schroeder 2010-02-07 22:26:43 UTC 
I was trying to print, using my HP Deskjet 3740 printer. SELinux evidently saw my attempt at printing as a "write" violation. Since I need to use my printer, a bug fix should be sent as a routine update, to allow printing. Seems simple enough. I shouldn't have to go through any reconfiguration, since this is an ordinarily expected process, not an exception.
Comment 3 Daniel Walsh 2010-02-08 20:24:07 UTC 
Did the other bug address your problem?
Comment 4 Philip Schroeder 2010-02-09 05:48:55 UTC 
We've documented the "bug," so is there a patch that is being pushed to everyone? As I said, I don't see that I should have to anything special to work around the problem.