Bug 467170
Summary: | SELinux is preventing scalc.bin from changing a writable memory segment executable. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Allan Engelhardt <allane> |
Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | caolanm, dtardon, jnavrati |
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: | 2008-10-16 14:05:11 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
Allan Engelhardt
2008-10-16 07:36:40 UTC
You probably wanted to say [setsebool allow_execmem off] in step one. Nevertheless, I don't see any AVC. My selinux-policy is 3.1.1-97.fc9.x86_64 . OOo follows the pattern of http://people.redhat.com/drepper/selinux-mem.html to get the executable memory that it needs. That hasn't been a problem with our selinux policies previously, so unless someone has changed our policies recently then more than likely the error is coming from some *other* library that OOo is linked to or dlopens and we get an error blaming OOo. So did you have any new openGL libraries, i.e. those of third parties like nvidia or something of that nature ? This looks odd as well: " Source gnome-screensav Source Path /usr/libexec/gnome-screensaver-gl-helper Source RPM Packages openoffice.org-calc-2.4.1-17.6.fc9 " Why mention of scalc.bin and openoffice.org-calc (which match eachother) but then mention of "gnome-screensaver" and "/usr/libexec/gnome-screensaver-gl-helper" which match eachother, but not OOo. Maybe that adds weight to the theory of a common underlying opengl library issue Comment #3 looks interesting and suggests to me that this may be a duplicate of Bug 465583 and Bug 467045 ?? Does OpenOffice interact with the screen saver in some way? I see the same message with the other OpenOffice applications but not with any other applications I have tried. OOo knows about the screensaver so as to turn it off while a presentation is running full-screen, but I suspect it may be more to do with opengl, e.g. try running glxgears or some other opengl using application. I say a rawhide selinux package in todays rawhide report that mentioned an opengl labeling change/fix Caolan McNamara said in Comment #2: > So did you have any new openGL libraries, i.e. those of third parties like > nvidia or something of that nature? Guilty as charged! I uninstalled the nvidia modules from Livna and I also uninstalled preload (which was gobbling up all the memory after the update) and now OOo is fine. Apologies for the false alarm :( Setting to Closed / NOTABUG (in Fedora). |