Red Hat Bugzilla – Bug 1289328
SELinux is preventing cupsd from rename access on the file /etc/cups/printers.conf.
Last modified: 2016-12-20 11:44:15 EST
Description of problem:
While following journalctl, noted SELinux blocking cupsd from modifying its own configuration file.
python3: SELinux is preventing cupsd from rename access on the file /etc/cups/printers.conf.
***** Plugin restorecon (99.5 confidence) suggests ************************
If you want to fix the label.
/etc/cups/printers.conf default label should be cupsd_rw_etc_t.
Then you can run restorecon.
# /sbin/restorecon -v /etc/cups/printers.conf
***** Plugin catchall (1.49 confidence) suggests **************************
If you believe that cupsd should be allowed rename access on the printers.conf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep cupsd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Version-Release number of selected component (if applicable): 2.1.2-1
Name : cups
Arch : x86_64
Epoch : 1
Version : 2.1.2
Release : 1.fc23
Size : 4.8 M
Repo : @System
From repo : updates
Summary : CUPS printing system
URL : http://www.cups.org/
License : GPLv2
Description : CUPS printing system provides a portable printing layer for
: UNIX® operating systems. It has been developed by Apple Inc.
: to promote a standard printing solution for all UNIX vendors and users.
: CUPS provides the System V and Berkeley command-line interfaces.
Occurs occasionally, especially during dnf update with cups update.
Steps to Reproduce:
Expected results: No complaint from SELinux.
Does the /etc/cups/printers.conf have correct context ?
# ls -lZ /etc/cups/printers.conf
If not, please run
# restorecon -v /etc/cups/printers.conf
$ ls -lZ /etc/cups/printers.conf
-rw-------. 1 root lp system_u:object_r:cupsd_rw_etc_t:s0 2751 Feb 12 11:56 /etc/cups/printers.conf
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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'
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.