Bug 129025 - cups writes /usr/share/printconf/util/backend.pyo, fails if /usr/share is not writable
Summary: cups writes /usr/share/printconf/util/backend.pyo, fails if /usr/share is not...
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer   
(Show other bugs)
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
Blocks: FC4Target
TreeView+ depends on / blocked
Reported: 2004-08-03 05:33 UTC by Tom London
Modified: 2007-11-30 22:10 UTC (History)
3 users (show)

Fixed In Version: 0.6.134-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-16 16:36:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tom London 2004-08-03 05:33:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040625

Description of problem:
cups appears to open /usr/share/printconf/util/backend.pyo for writing.

This fails if /usr/share/.... is not writable, or if running with
strict SELinux policy.

Perhaps making /usr/share/printconf/util/backend.pyo a symlink
(say, to /etc/cups/backend.pyo)......

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. boot system with USB printer (say, HP 950PSC), and /usr/share
read-only, or with SELinux strict/enforcing

Additional info:

Comment 1 Tim Waugh 2004-08-03 08:13:55 UTC
Fixing component.

Comment 2 Tim Waugh 2004-08-03 08:16:13 UTC
Apps that ship Python code should also ship the .pyo/.pyc bits IMHO --
but apparently this is not trivial to do correctly.  CC'ing Python
maintainer for further input.

As far as SELinux goes (and I think this is what prompted this bug
report) these should be dontaudit, and I thought they were at one point.

Comment 3 Tom London 2004-08-03 14:23:57 UTC
dontaudit would remove the avc's, but the write of the file would fail.

That would be OK if the the .pyo is never used, but then ....


Comment 4 Tim Waugh 2004-08-03 14:31:47 UTC
The .pyo file is just to speed up loading of the Python module -- it
is for optimization, which in this case is lost in the noise of having
to load the foomatic database later on.

Comment 5 Tim Waugh 2004-12-22 15:56:30 UTC
Waiting for redhat-rpm-config to turn on the Python pre-compilation.

Comment 6 Tim Waugh 2005-03-17 16:53:36 UTC

Comment 7 Elliot Lee 2005-03-22 04:43:21 UTC
Tim - if you'll tell me what changes to make, I can do that, or feel free to
just check in the necessary changes yourself.

Comment 8 Tim Waugh 2005-03-22 11:36:48 UTC
/usr/lib/rpm/brp-python-bytecompile needs to get run in

Comment 9 Elliot Lee 2005-04-07 03:18:09 UTC
Enabled in redhat-rpm-config CVS, it'll wind up in the dist sooner

Comment 10 Tim Waugh 2005-04-18 13:55:39 UTC
Please build this.  Thanks.

Note You need to log in before you can comment on or make changes to this bug.