Bug 194586
Summary: | cupsd doesn't start on fc5 with selinux enabled | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Oliver Mangold <o.mangold> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | triage |
Target Milestone: | --- | Keywords: | SELinux |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-06 15:59:49 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
Oliver Mangold
2006-06-14 08:38:08 UTC
Why is cups trying to read users Home directories? Why is it requireng execstack? It should not I don't see this here. If you run this command, as root, what output do you get?: rpm -ql cups | xargs restorecon -v (In reply to comment #1) > Why is cups trying to read users Home directories? I'm not sure. I didn't do any cups configuration explaining that. I just installed my printers using system-config-printer. The only reason I can imagine would be, that I installed some fonts being in a user home directory. Is this a problem? > Why is it requireng execstack? It should not Really don't have any idea. (In reply to comment #2) > If you run this command, as root, what output do you get?: > > rpm -ql cups | xargs restorecon -v > It doesn't say anything. I'm not familiar with selinux. Does this mean, the security contexts of cups are not set? Are you still getting this? I've never been able to reproduce it here. > Are you still getting this? I've never been able to reproduce it here.
I just took again a look on this. Cause Daniel said, it shouldn't need
execstack, I took a look on the cups source. To me it seemed to, that it doesn't
need it, so I rebuilt cups and installed it. This solves the problem. But after
reinstalling the original .i386-package, it the same as in the beginning.
I assume, that after the every update I'll have to rebuild it again (I tried
cups-1.2.1-2.i386.rpm, and it still has the bug).
Quite funny, that the compiled one is that different from the source.
I expect the difference is just the initscript -- we looking in the wrong package. :-) The audit messages seem to be due to /usr/share/printconf/util/backend.py. So what does 'rpm -V system-config-printer' say? It says nothing. Seems to be the original. The package is system-config-printer-0.6.151.7-1 (just for the case that this helps you with anything.) *baffled* Fedora Core 5 and Fedora Core 6 are no longer maintained. Is this bug still present in Fedora 7 or Fedora 8? Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |