Bug 585723
Summary: | selinux alerts after fedora 13 restart | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | hal |
Component: | gnome-color-manager | Assignee: | Richard Hughes <richard> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | dwalsh, mgrepl, paul.lipps, rhughes, ricardo.arguello, richard, rstrode |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-05-18 12:46:10 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
hal
2010-04-25 19:13:16 UTC
Are you running with NIS? No - or at least not that I'm aware of. This is an isolated virtual machine running under vmware fusion on a macbook pro OS X 10.6. I did select a fair number of optional items during the install (mostly development tools), but other than that, I haven't added or configured anything beyond the installer defaults. Ok, I am just wondering why gcm-apply would try to listen/bind on port 8614? No idea. Let me know if you want me to dig through any logs or other files looking for clues. Richard Hughes suggests that gcm-apply is calling sane_init which is causing this AVC. He also states that it no longer needs to call this. Can we get a version of gcm-apply that does not call sane_init? Could you grab the gnome-color-manager .src.rpm package from here please: http://people.freedesktop.org/~hughsient/fedora/13/SRPMS -- rebuild it and then install it, and then verify that it no longer produces a SELinux notice. Thanks. *** Bug 590467 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 588295 *** |