Bug 1305961

Summary: boomaga requires the SELinux security policy to be set to Permissive (or Disabled) to function
Product: [Fedora] Fedora Reporter: xvr <smith93_28>
Component: boomagaAssignee: MartinKG <mgansser>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 23CC: mgansser, mikhirev
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 18:35:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description xvr 2016-02-09 16:52:38 UTC
Description of problem:
boomaga requires the SELinux security policy to be set to Permissive (or Disabled) to function. Otherwise, if SELinux is set to Enforcing (the default mode under Fedora), boomaga can't print (and a problem is logged).
By setting the policy to Permissive, one can print to boomaga (but an problem is still logged).

Version-Release number of selected component (if applicable):
0.7.1-6.git9a6aa75.fc23

How reproducible:
always

Steps to Reproduce:
1. Install boomaga with dnf, or build it from source (git) and install
2. Try to print a document to boomaga
3.

Actual results:
- if SELinux is set to Enforcing, nothing is printed and the boomaga virtual printer is immediately disabled. Error conditions are logged by SELinux.
- if SELinux is set to Permissive, the document is correctly printed but error conditions are still logged.

Expected results:


Additional info:
There is no such problem under OpenSUSE Tumbleweed, with boomaga built and installed from source (git)

Comment 1 Fedora End Of Life 2016-11-24 15:28:54 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

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 23 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.

Comment 2 Fedora End Of Life 2016-12-20 18:35:41 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.