Bug 525583
Summary: | SELinux is preventing /usr/bin/empathy "execmem" access on <Unknown>. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mathieu Bridon <bochecha> |
Component: | empathy | Assignee: | Peter Gordon <peter> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | bdpepple, peter, xan |
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: | 2009-09-25 15:03:12 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
Mathieu Bridon
2009-09-24 22:05:47 UTC
Note that this happens consistently when using an Adium theme, so it might be an issue in WebKit. So, I really have no clue of what this might be, but here's one wild guess: can you compile WebKitGTK+ *without* JIT (--disable-jit) and check if that fixes it? I'm using Fedora and can't really reproduce this though, is there any non-standard setting I should enable? No non-standard setting enabled, just Fedora Rawhide with empathy 2.28, and selinux enabled (by default). (In reply to comment #3) > No non-standard setting enabled, just Fedora Rawhide with empathy 2.28, and > selinux enabled (by default). OK, I'm running Fedora 10 still, so it might be that. I'll upgrade to Fedora 11 (or maybe some F12 alpha/beta) before going to the Boston Summit probably, so I'll make sure to check that if we don't fix it before. In any case, if you can test what I suggested that would be very useful. I'll try that this week-end. You won't be able to reproduce it with F11 though. It only happens when I try to use an Adium theme, so it needs 2.28. Thanks for the bug report; However, I'm almost certain this is the same issue as seen in #516057, caused by some erroneous assembly in WebKitGTK+'s JIT support. If this is not the case, and something else is indeed causing the problem, please re-open this bug with further details. *** This bug has been marked as a duplicate of bug 516057 *** |